Live data from Hacker News

Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

news.ycombinator.com

41–50 of 275 posts

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#41
post #22

I'd argue differently. Congrats for having the courage to recognize your problem. The analogy that comes to mind is I've been playing basketball in my local town, and now I've gotten promoted to play in the big city. I now feel like a small fish in a big pond. If you enjoy software engineering, I'd say, double down. Now that you're at the medium software company, seek mentorship and coaching from others. In addition,…

> Now that you're at the medium software company, seek mentorship and coaching from others.

Agreed. My abilities as a developer increased tremendously at one of my jobs, and I can attribute 90% of that to a single person at that company who mentored me and helped me grow. (Hi, René, you probably don't read this.)

You can read all the articles and books you want, but actively pairing with someone on tasks and getting personalized feedback has a much greater pay-off.

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#42

Do you want to be a software developer still? (That isn't clear from your summary). If so, you need to learn better habits. I suggest picking up a book on the subject, like "Code Complete" (at Amazon or wherever books are sold. Pretty sure it's at the library if you'd rather read it for free -- but it'll do better as a reference book on your desk for a few years). Use it and start practicing with personal projects ho…

To your last point, it doesn't sound like algorithmic and practice problems are really OP's issue, as they suggested they can solve almost any problem given but do so in a way they now feel is amateur or hack-ish.

In a similar line of thinking to your Code Complete suggestion, a book like Architecture of Open Source Applications[1] might also be a good fit.

1 - http://aosabook.org/en/index.html

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#44
+1 for being self aware.

The question you need to ask is simple; What do you want to do?

Just because you've come to the realization that you're not a good coder doesn't mean you cannot become a good coder. Most of software engineering is not about being clever. It's about being well organized and paying attention to details. Experience is largely gained, and wisdom learned, from screwing up. Then being able to recognize the screw up and understand how to prevent it in the future.

I have a firm conviction that most people can become productive software engineers. The main impediment I've seen to getting better is lack of interest in programming or an inability to learn from past mistakes. This is why I gave your show of self reflection a +1. The fact that you are asking yourself this question, and doubting your ability, tells me you are willing and interested in learning from your mistakes.

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#45
Just realizing this and being able to verbalize this makes you way better than 90% of people in IT.

Most senior consultants in Accenture are big dummies that know tech buzzwords. Most of them have never used an IDE.

So I would say your doing good. Don't worry you are good software engineer.

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#48
The only way to get better is to practice. I didnt code for about 15 years while I ran my own company and only started coding again about 3 years ago. My brain feels like mush sometimes.

Start by modifying other people's code - fixing bugs. When you have to write new code model it after other peoples' structures. Write comments for how the logic should work before you write the actual code.

You can get it working in one big method using hardcoded values, then slowly break it apart. It might be you just stopped your code at the first draft.

Alternately you can do product management. Being technical and doing product management means you can actually understand what is going on under the hood.

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#49
Suggestion: I've found that doing a graduate CS degree really helps me build a theoretical foundation which has made me much better at my work. Example: a much deeper understanding of the HTTP protocol and the client-server model, and how it relates to the world of networking and computing overall.

Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?

#50
>but some months ago I decided to go to work on a proper medium software company.

I'm barely sure what that actually means in practice, day-to-day. If that's really what it is, they should know how to help you get up to speed and understand your situation.

Your core feelings here (not to be dismissive) seem to be about them "finding out" and suddenly firing you. It's remotely possible they do that, but unlikely. Even if they do, it was just a company you don't qualify for. It doesn't diminish the previous work you've done.

There's a lot of advice here already about what to do within this company, so consider the worst case: you fail 2-3 more times and they ultimately fire you. You still have something to fall back on by going back to your previous work.

Post reply on HN