I believe this is a time when a lot of software engineers are asking the hard questions about their careers. Here's why: The technologies have become simpler and the barriers to entry have become low. Once upon a time, if you knew the mainstream languages (C++ and Java) it meant you paid your dues learning the hard stuff. Today, with nodejs becoming mainstream, and the cloud at the backend, developers who come from a…
Ask HN: Have you successfully done a career do-over, and how did you do it?
11–20 of 180 posts
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#12I believe this is a time when a lot of software engineers are asking the hard questions about their careers. Here's why: The technologies have become simpler and the barriers to entry have become low. Once upon a time, if you knew the mainstream languages (C++ and Java) it meant you paid your dues learning the hard stuff. Today, with nodejs becoming mainstream, and the cloud at the backend, developers who come from a…
Give it five years or so as the business needs of those companies change and the codebases become more and more expensive to maintain. :)
Focusing on the technological complexity is a bit of a red herring, at least as many problems come from having to keep up with the complexity inherent in dealing with an ever-changing "real world." Usually you can't just flip a switch from A to B, you have to support old workflows/clients, new workflows/clients, transitional modes, etc.
We don't have any real sort of "engineering standards" for software development. Unless/until we find those, it's very hard to claim that the workers will be reduced to interchangeable cogs. We don't really even know what those cogs need to do to make sure a codebase doesn't become a big mess, today, based on the codebases I've seen.
Without that, developing meta-/organizational-/design- skills, instincts, and creativity can be very powerful. Being able to sell that effectively without necessarily having to aim for management positions might be a bigger trick, but it's hardly impossible.
But even if you try to make your calling card something like e.g. a "node.js+AWS stack" expert, you've probably got a significant amount of future work at least in maintenance for all the companies that build themselves on that stack today. Maybe that's not what you want - in that case stay on the new-tech treadmill if you don't want to do more design/architectural/organizational stuff - but it's something that will be needed, at least.
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#13I believe this is a time when a lot of software engineers are asking the hard questions about their careers. Here's why: The technologies have become simpler and the barriers to entry have become low. Once upon a time, if you knew the mainstream languages (C++ and Java) it meant you paid your dues learning the hard stuff. Today, with nodejs becoming mainstream, and the cloud at the backend, developers who come from a…
The ability to quickly learn and adapt is in my opinion an important part.
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#14Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#15Are you talking about someone who screwed up enough times that the mean free distance to a negative referral is essentially 1.0 ? I don't see industries as having 'eyes' but I have known industries that are relatively small communities.
I have known, and hired, a number of people who have 'redone' their career when the thing they started with didn't pan out, a chemist into a QA person, a semiconductor process engineer into a UNIX developer, a mom into a product manager. That sort of 'do over'.
And I've met folks who 'grew up' in a company doing one thing for 15 to 20 years and then failed to find an opportunity to continue doing that thing. Only to switch into a different career all together. Most commonly that is, "Hey you weren't you 20 years at BigCorp? What are you doing these days, 'mostly consulting'" sorts of conversations.
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#16I believe this is a time when a lot of software engineers are asking the hard questions about their careers. Here's why: The technologies have become simpler and the barriers to entry have become low. Once upon a time, if you knew the mainstream languages (C++ and Java) it meant you paid your dues learning the hard stuff. Today, with nodejs becoming mainstream, and the cloud at the backend, developers who come from a…
>developers who come from an "html programming" background can now build scalable and enterprise grade applications without breaking a sweat. This is a popular misconception but inaccurate nonetheless. It may appear that way at first glance, but there is still more to building "scalable and enterprise grade" stuff than just cobbling together a bunch of off the shelf components.
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#17I believe this is a time when a lot of software engineers are asking the hard questions about their careers. Here's why: The technologies have become simpler and the barriers to entry have become low. Once upon a time, if you knew the mainstream languages (C++ and Java) it meant you paid your dues learning the hard stuff. Today, with nodejs becoming mainstream, and the cloud at the backend, developers who come from a…
If anything threatens software engineers, it's probably the rise of automation capable of making the "basic web app" people obsolete. I snigger at myself when I contemplate some kind of AI which could do this, although the idea seems less crazy when viewed in the context of many companies and individuals who have attempted to create a "build anything fast" framework/service/ecosystem/etc. Perhaps it does take an AI.
Otherwise we're pretty safe, methinks. Carry on, no need to try for a career change, unless you're really sick of the job itself, in which case the world is your oyster.
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#18If you're not getting any offers that's one thing I guess, but imposter syndrome is real in the industry. We all worry about being up to some rockstar level and all the grueling interview processes out there. Then we brush up for a couple of weeks, hit the market, and field multiple offers again.
Re: Ask HN: Have you successfully done a career do-over, and how did you do it?
#19I believe this is a time when a lot of software engineers are asking the hard questions about their careers. Here's why: The technologies have become simpler and the barriers to entry have become low. Once upon a time, if you knew the mainstream languages (C++ and Java) it meant you paid your dues learning the hard stuff. Today, with nodejs becoming mainstream, and the cloud at the backend, developers who come from a…
That's complete nonsense. As a system grows, so does its complexity. And no amount of libraries and fancy languages can turn a complex distributed stack into a simple straightforward thing. If you you have deep knowledge of whatever you're working on (be it the deepest ins & outs of C++ or nodejs), you're worth your weight in gold.