I would like to leave because the stress of keeping up to date with frameworks and the competition is just brutal. Everything is just so complex to implement these days. I still love troubleshooting systems and doing hands on work that doesn’t involve writing code with other SWEs, so I’m considering what options I have. I basically don’t want to be part of a code review or design discussion ever again.
Ask HN: Former software engineers, what are you doing now?
161–164 of 164 posts
Re: Ask HN: Former software engineers, what are you doing now?
#162I wasn't quite a software engineer, but a data analyst/scientist/engineer/term-du-jour at a brand-ish name software company for ~8 years, so pretty close in terms of the day-to-day work and culture. 1) I'm a professional cartographer, sort of. I make wooden topographic maps. 2) A bunch of reasons. I was never "supposed" to work in software -- I went to school in mechanical engineering, and wanted to get closer to som…
Re: Ask HN: Former software engineers, what are you doing now?
#163When I got bored with software engineering, I decided to invest in developing leadership skills and to try to build teams. Many people (myself included) are motivated by the impact their career can have. The impact of a great leader is exponentially larger than that of a direct contributor (based on the number people they can typically influence, and the amount of resources at their disposal to pursue “bigger” ideas)…
How did you make the transition in the first place? My issue is that despite enjoying and having good leadership skills (based on external feedback so I'm reasonable sure that's not just my ego ) I'm not the strongest technically and getting into those roles seems to require becoming an extremely technically competent senior/principle engineer first.
I don’t believe you have to reach this level across a wide domain, but you should be able to achieve it within some reasonably narrow technical scope. If you don’t, you will not be able to lead a technical team effectively. When you are in leadership, you may not always be on the hook for delivering, but you can win major support from your team if you are capable of diving in and doing something technically impressive from time to time. In addition, you will need to be able to teach engineers and guide technical implementation, which requires the ability to communicate clearly about deeply technical topics. I find that the less I know about a construct (think Law of Demeter, etc.) the less I’m able to communicate it to others or build solid arguments for or against it.
I think you must dig in and obsess about becoming great at engineering. My passion for this role is because of its meta nature. I love engineering and have built strong opinions about it over my career, and now I want to engineer a team of engineers who can see things similarly, and ultimately do greater things collectively. This wouldn’t be possible if I didn’t take the time to be a great engineer first.
Re: Ask HN: Former software engineers, what are you doing now?
#164At one point, a few years ago, I was in your place. Really bored and completely miserable. I got tired of huge companies (one in particular) and went to a "goldilocks zone" startup. By this I mean the ones were they have enough money to pay you well and a reasonable product/business with a high chance of success, but they're still small enough for you to have an impact in the organization (we were under a 100 people…
Been there. It was wonderful... and then pretty good... and then it got kind of boring. (I'm at 11 years.) It doesn't stay goldilocks forever. While it's good, though, it can be really good. Enjoy it while it's good, because it won't be forever. Things change. People change. Businesses change. Good situations become not so good, sometimes very quickly. If you're in a good situation, value it.
The point is that if you found it once, it's likely that you can find it again.
So far I've been on two such magical teams. Maybe there's a third one.