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

11–20 of 275 posts

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

#11
A long time ago, I described what I did as a programmer, and my friend said "Oh, so you get paid to learn?" I thought about it, and agreed. Part of programming is learning.

Sounds like you've got a great opportunity to learn what you don't yet know: you already have a list of things you know you need to work on, a codebase, and a job. Do you think one or more of your co-workers would be willing to give you feedback? Would you be willing to take time (maybe extra time, 'off the clock') to practice?

If, e.g., hard-coding is where you're at, maybe something like working your way through 'Code Complete' would be of help, but I would pair the reading with doing, as close to the company's codebase and personnel as makes sense.

I've heard tell of people who asked to be shifted to a lower-level position so they could work at the level they were comfortable with.

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

#12
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 hosted out of Github.

I also suggest using a daily practice like a code kata: http://codekata.com/

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

#14
post #3

>I'm not sure if I can be a PM if I'm not able to code things the right way myself. You don't need to know how to code the solution to be a good PM, it's a different set of skills. QA - writing testcases, automated regression tests is also a possible path. Lots of companies want QA engineers that can write automated regresion tests (selenium etc)

> "QA - writing testcases, automated regression tests is also a possible path."

No. QA automation code is still code. If a person can't write solid code, they're not going to succeed in QA doing automation either.

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

#15
most bad engineers I've experienced have no idea that they're even bad, in the sense they can't identify what's wrong with their code or even be aware of hacky patterns.

that you can self-critique would indicate you potentially have a great future of leveling-up ahead of you.

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

#16
Keep at it. Why would you quit just because you've realized that you've done some things the wrong way?

I get the feeling that quite a few engineers come at it from your kind of side. Only one dev, stuff needs to be done, it gets done with a lot of heaving and sweating.

Now you're in a larger place, there should be some breathing room. Find out how people do things:

- Maybe read the GoF patterns book to get some cookie-cutter solutions to common problems.

- A lot of the simpler DS&A learnings can be practiced with introductory leetcode problems. Don't sweat it too much, I'm sure there are a lot unuseful brainteasers there too.

- Get used to all the tooling around the code. Git, CI/CD. Build scripts.

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

#17

You know there are issues, so that is a good thing. Hang tight. You can clearly learn to fix these issues and become better at building/architecting solutions. Spend some time reviewing projects on github and see how others have tackled the issues you are struggling with. Practice by creating your own projects. They don't need to be complete but will allow you to try different strategies for structure, hard coded val…

[deleted]

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

#18
I’m a product manager partly because I’m not a great coder. Other engineers are faster and better, so I wanted to add value by helping figure out what they should actually be building based on user needs. It has its up and downs but you can still do well without being the most proficient coder.

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

#19
I’m not sure I really follow - what’s an example of a project you solved successfully before in “hacky” way?

When you get knocked off your horse you either give up or stand up. Maybe you are feeling it really hurt. But you’ve invested a lot in this industry and career, so don’t give up after your first real challenge. Get the fuck up and figure out how to deliver successfully on this project 1) what parts can you solve? Do those 2) for the parts you can’t, how can you? How do you break it down into specific problems? In this case, maybe one piece is centralizing hard coded variables into one place. What’s the best way to do that? Once you have specific questions, you’ll be able to find specific answers. Start working through them. If you can’t find self help, what about some colleagues you’ve amassed over 10 years? Worst case ask your manager, at some point you can’t bullshit things anymore, but give it an honest try first and outline what you were able to do and which problem(s) you are stuck on and what you tried already. Your manager will appreciate your ownership and your concrete ask for help.

Context: I made a career change and got fired from my first job 5 months in. It was devastating, but I got back up and got another job. I got a second job, went ok until i got a manager who said I was focused on the wrong things. After a year he kept complaining about it and in the end gave me a bad performance review. It left me shaken. I got back up and got a third job, where I am today, and I am crushing it. I still doubt myself, I still have wounds from before, and I even have doubts sometimes if I could succeed elsewhere, but I keep getting better, and getting up when I’m knocked off.

Good luck

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

#20
My company is starting to move away from custom software development for our clients in favor of leveraging and configuring commercial software packages and services. You might need to create a python script or a make a few API calls, but most of the job is learning how to get the software to solve the client's business needs. Maybe you would enjoy that more? Maybe we could switch jobs. :)
Post reply on HN