Live data from Hacker News

Ask HN: Average coder at dead-end. What now?

news.ycombinator.com

11–20 of 62 posts

Re: Ask HN: Average coder at dead-end. What now?

#11

With your attitude, I wouldn't hire you either. Buck up, little camper! Welcome to the internet! You made no mention of open source apps you've written or contribute to. You also made no mention of any side projects you've done that don't have that 'bold and pink' your work projects do. With no drive to improve your skills, you're destined to stay in this dead-end job, if you're not replaced soon by someone who will…

+1 for Open Source

Since you have a php background I recommend looking into Drupal. It's in high demand right now & with Drupal 7 I see the demand for talent increasing even more.

Re: Ask HN: Average coder at dead-end. What now?

#12
If you can honestly say that you get always get everything done on time then that's huge. If you say that the design on these websites isn't your idea then I think potential employers would be understanding, but better would be to build something simple on your own that shows what a website looks like when you do it your way.

Re: Ask HN: Average coder at dead-end. What now?

#13
I sympathize; I was in a simliar situation around five years ago.

There are three things I've done which have been responsible for literally every job I've had in the last decade. In order of importance, they have been:

1. Know people. 2. Engage in the FOSS community. 3. Challenge myself.

That's it. Now, the interesting thing is that if you reverse this list, you get the steps you need to get a new job:

3. By challenging yourself, you will increase your knowledge base and become a better coder. 2. Find an project, tool, or subject that interests YOU. Something YOU would find useful and rewarding. Whatever it is, write it and RELEASE IT. If there's a project that already does what you want, start contributing. Help other people use it. Write documentation. Anything. Whatever it is, RELEASE IT. Doesn't matter if it's something a hundred people worldwide will find interesting - you'll get their attention, which leads to… 1. Knowing people who can get you jobs.

I cannot stress this enough: RELEASE CODE. The great thing is that you can usually get your employer on board with this. If other people use it, they can contribute features and bugfixes back, which they can make use of. It's like having programmers work for them for free.

The fact that you have this ambition at all puts you at a significant advantage over other programmers. Keep hold of that drive.

Re: Ask HN: Average coder at dead-end. What now?

#14
post #2

The typical engineer is not a genius. Don't compare yourself to geniuses. The typical engineer also makes more than you do, and you should find a job and close that gap. If you are feeling like you are unworthy, go talk to any chaps in London about the guys making 50k sterling while being unable to do FizzBuzz. (I assume you have them in London, too.) If you're worried about your portfolio being insufficiently graphi…

Is FizzBuzz actually used as a coder test? Are their really paid coders out there who can't solve that in a couple minutes?

Re: Ask HN: Average coder at dead-end. What now?

#16
A lot of people are recommending writing some open source software. I would advise against that. Instead I would advise writing some software that you find to be useful. That does not rule out contributing to an open source project, it just makes it less likely you'll waste your time. It's really really hard to figure out if people really need the features they ask for in open source projects -- and I think there are a lot of bloated FOSS products out there. Write something for yourself and it may lead you down a surprising path.

Re: Ask HN: Average coder at dead-end. What now?

#17
post #2

The typical engineer is not a genius. Don't compare yourself to geniuses. The typical engineer also makes more than you do, and you should find a job and close that gap. If you are feeling like you are unworthy, go talk to any chaps in London about the guys making 50k sterling while being unable to do FizzBuzz. (I assume you have them in London, too.) If you're worried about your portfolio being insufficiently graphi…

Is FizzBuzz actually used as a coder test? Are their really paid coders out there who can't solve that in a couple minutes?

Yes. Yes.

Re: Ask HN: Average coder at dead-end. What now?

#18
post #2

The typical engineer is not a genius. Don't compare yourself to geniuses. The typical engineer also makes more than you do, and you should find a job and close that gap. If you are feeling like you are unworthy, go talk to any chaps in London about the guys making 50k sterling while being unable to do FizzBuzz. (I assume you have them in London, too.) If you're worried about your portfolio being insufficiently graphi…

Is FizzBuzz actually used as a coder test? Are their really paid coders out there who can't solve that in a couple minutes?

Of course.

If you can't understand how this can happen you need to read The Peter Principle.

http://en.wikipedia.org/wiki/Peter_Principle

Re: Ask HN: Average coder at dead-end. What now?

#19
post #2

The typical engineer is not a genius. Don't compare yourself to geniuses. The typical engineer also makes more than you do, and you should find a job and close that gap. If you are feeling like you are unworthy, go talk to any chaps in London about the guys making 50k sterling while being unable to do FizzBuzz. (I assume you have them in London, too.) If you're worried about your portfolio being insufficiently graphi…

Is FizzBuzz actually used as a coder test? Are their really paid coders out there who can't solve that in a couple minutes?

That's why it's so popular :(

Re: Ask HN: Average coder at dead-end. What now?

#20
post #7

By your statement....you are no rockstar. I would argue that...you are no rockstar YET. You need at least two things to become a Genius/Rockstar/whatever: 1. Challenging work that forces you to improve your c0ding ski11z. 2. Time. There is no shortcut and your eight years so far count quite well. It is time to take it up a notch and start challenging yourself in your current job or trying some side projects. If you d…

I would say that you also need "3. Groupies". I really dislike the "rockstar" moniker, but positive reinforcement is important, especially if it appears as if you're stuck. That's one of the good things about the open source world, where it's easy to have a small, popular project. The sheer amount of project and time management skills teaches you is much greater than the improvement in coding ability (which really isn't that linear).

If you do a decent job of presenting and updating such a project, people will like it and probably let you be aware of that fact. And even the most lone-wolf programmers need that, whether they admit it or not.

This could be done at work, too, by making some utilities or introducing new features for the benefit of you co-workers or customers. Most of the time, the feedback isn't as direct, though.

Post reply on HN