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

111–120 of 275 posts

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

#111
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,…

I don't think I've come across coursework that's intended to level up coding ability itself (i.e. good software engineering/design) rather than teaching basic knowledge things. I'm curious if anyone has come across anything of that nature.

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

#112

I started programming at gymnasium and through uni. Throughout uni I did a lot of Competitive Programming. Most programs in CP are written and discarded within hours of each other. You also pretty much only use the standard library and no third-party tools. You never interact with the hardware of the system that the program runs on. Maybe reading files from the filesystem (depending on judge software) but definitely…

> Essentially you become an expert in writing 100-200 lines of code that reads data from standard input and prints data to standard output. Useful for CP, not so much in the real world.

Skills from CP transfer very well to the current FAANG interview coding olympics. Add some soft skills and you can easily land a job where you can learn the rest of the things you're listing there, while getting paid. So I wouldn't say there's not much use in the real world.

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

#113
post #107

We hired someone like this last year who was a lead in the last role at a small firm, had senior titles over a couple roles prior. This person is smart and well-liked and called out their concerns early on, so we're working with them and have seen considerable improvement in the half-year since they were hired. So I'd say it really comes down to your environment. If you have a good, supportive culture, I would have a…

We had a similiar issues where a senior employee came and interviewed great. She ended up becoming a pm. At another place something similiar happened and she ended up as a pm / developer. I think pm move is a great idea for someone who can sell but maybe isn't as strong. Perhaps moving to pm is a good answer for thread poster.

My attitude about this is, if it's not really the person's fault (ie. learning bad dev hygiene from bad teams) and they want to continue as an engineer then they should make an attempt.

There are of course people who at the end of the day just don't have a knack for this stuff, and in that case, I certainly agree.

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

#115

It's not clear from your post (and you don't have to make it clear, of course) whether you're getting fired from your current company or not. Merely failing one task won't get you fired and if you have the self-awareness demonstrated above to realize that you haven't yet learned what you need to become senior, gives you a clear path (and one that won't even be that hard if you've been selling and making software for…

I remember one from Java ~20 years ago:

   public final static string HTTP = "http";
   public final static string COLON = ":";
   public final static string SLASH = "/";
   public final static string WWW = "www";
with code like

string url = HTTP + COLON + SLASH + SLASH + WWW ....

Ignore any Java issues - not used it much in ~15 years.

Edit: I asked the developer who had written this what it was achieving and he said it was best practise ;-)

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

#116
Are you sure you’re just not used to the way things are done at bigger companies? When you work in a small team or by yourself on small projects, you might not encounter the opportunity to fully flesh out solid architecture and coding practices because it’s not in the budget.

I imagine after a little while working in a different environment, you’d adapt to the new way just as you had adapted before.

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

#117

I started programming at gymnasium and through uni. Throughout uni I did a lot of Competitive Programming. Most programs in CP are written and discarded within hours of each other. You also pretty much only use the standard library and no third-party tools. You never interact with the hardware of the system that the program runs on. Maybe reading files from the filesystem (depending on judge software) but definitely…

For context: The word "gymnasium" outside of Germany refers to a place where you do sports, inside of Germany it describes the "highest" out of the three typical types of secondary schools.

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

#118
Don't be discouraged! Sounds to me like you're just growing up.

Young developers (in both actual age and years of experience) tend to think they're amazing and better than others. (This is true in many/most fields, and was very true for me.) And then as you get better, you discover how much you don't know, and start to feel worse and worse about your abilities.

There was an XKCD comic about this, but I can't find it. In essence, given any field, the journey looks something like:

1. I don't know how to do X, so I'm going to learn.

2. Wow, X is awesome and I'm awesome at it!

3. X is a little more complicated than I realized.

4. OMG, X is hard and I'm shit at it.

5. Maybe I should give up on X.

6. Well, I'm not the worst person in the world at X. Bob's worse than I am, and still somehow gets paid for it.

7. I can now see all the things I don't know, but at least I can start learning them, one by one. This is going to take a while.

8. I'm now better than most, but there will always be more to learn and someone better than me. I accept that I will forever be a student at X, and so is everyone else.

Or, as the old adage goes: Fools think they're wise. The wise know they're fools.

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

#119
I had to respond on this one! I'm 47 and don't code "full time" anymore, but do spend at least 20 hours a week coding (mostly because I love it, partly because it's good as a business owner to look for better ways to cut costs and improve the UX at the same time). If you have some domain level expertise for a particular field and _also_ know how to code you will do very well indeed. You will do great if you know where your weaknesses are and work on them. The best coders I have ever worked with were folks that were humble and knew they didn't know $%&!. So the fact that you are willing to say you aren't great makes me believe you are better than you think.

My only advice (disclaimer not a sage here) is to continue to specialize in an areas that hasn't been commoditized yet and to work on the process, rather than the specific technology. You don't need to know all the "secrets" of a language to make you more productive. That will allow you to charge higher rates than for example commodity developer. Also, another great way to work on weaknesses is to teach others, learn by teaching as they say.

I'm sure you will do great things keep it up, love your attitude.

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

#120
post #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

About Code Katas -- agreed. They can be used from simply an algorithmic learning viewpoint. They can also be used like an athlete uses weightlifting: Over time, certain motions become second nature.

When you're talking about such a mentally heavy discipline, it helps to have certain behaviors happen effortlessly. You might otherwise learn these things over time with a large team, but I think certain brains needs this kind of practice.

Just like there are different ways of learning any subject, there are different ways of maintaining proficiency (IMHO).

Post reply on HN