To point straight at the childhood desires behind it all, I like receiving puzzles to work on and I like wowing people by anticipting their needs and exceeding their expectations.
One can frame management/executive-track work that way too, but the third desire is to do that in the peace and quiet of my own space and (mostly) on my own time -- so for me it all pointed back to increasingly sophisticated remote contract work and using my entrpreneurial blood and commmuniction skills to facilitate it.
I don't think anybody can predict what direction you might want to go, but I do suggest you think about what you're really after in your career and which of your opportunities are more or less aligned with that.
Cargo cult startups followed along by naiviete and businesses that had to compete for their same pool of talent followed along by necessity.
But those compensation packages are disconnected from the value generated by the engineers and eclipses it in almost every business and division, so it's not sustainable. The big layoffs are a first part of the correction, and a quieter adjustment will happen as non-cash compensation (options, stock grants, etc) calibrates itself into today's more grounded economy.
The managers saying "80k is a high salary" to you are give-or-take correct (assuming you're in a mid/low cost of living area). Software engineering remains a hot market with lots of money flying into it and will pay better than other engineering fields for a while longer, but ultimately pegs into the same "professional middle class" bucket as the rest.
If you want to be filthy rich, software engineering is only the right choice when you have an opportunity to ride one of the boom waves and FIRE yourself. You probably won't have that opportunity again for years if you aren't on today's cresting wave already. That's the second hill in your bimodal distribution and it's a dwindling aberration.
But if you just like writing software and being financially secure, the first hill is pretty great.
Thats incorrect. Statistics show that those who take most share out of the economic value that they generate are the higher paid tiers of engineers in Silicon Valley. And even they get at most a 10% of the actual economic value they generate.
This means that not only those engineers are already being paid WAY less than the actual economic value they generate, but also the majority of the population receive only a pittance from the economic value they generate.
Management earns more money. Partly because they control how the money is spent. Partly because they're a value-multiplier.
Coders get to write code.
You seldom get both [1].
So for each person, it's really important to understand your root motivation. If it's money, then climb the ladder. It's gun in a different way, and if done well, can bring satisfaction.
However, if writing code is eat gets you out of bed, if meetings are something you detest, then perhaps "enough money" is enough, and you might prefer enjoying your path through life.
[1] you seldom get both in a large company. However in very small companies, and one-man operations, you can often find a very lucrative niche. Fewer people means little management (although more time talking to customers) so you get to spend more time actually producing.
I would choose to write C even in an oldschool world where it only paid $50k. I even do it at home for fun!
Java[Script] or C# though? Nah; I'm going back to school or something.
What a weird professional dynamic.
Cost of living always anchors these discussions. You can't compare FAANG salaries in very high cost of living areas against somewhere like the midwest.
This is also a question of leverage: they're able to find developers by paying 80k, so they continue doing that. If you had something they needed but wasn't as readily available, then you could start discussing what it looked like to be paid more.
To put it another way, my favorite thing about programming is the creative aspect. Getting a problem, thinking of a solution and then writing the code that solves it is more rewarding than anything the higher positions have to offer.
I studied compilers during this time. Dynamic typing + production systems are a waste of life. :)
> Fast forward to today and I sling TypeScript / Angular / Java as a Senior Software Engineer
Yeah, TS is good enough for me now. I swapped Angular for Svelte in there, but otherwise the same. Enjoying learning the frontend now that it is somewhat sane.
> [They're] still expected to support every app they have ever worked on and do 8+ hours of meetings a day. The pay is more but so is the stress. I have a great family and just want to enjoy my life.
> I see the burnout above me
Yeah. Leadership imposes a large emotional cost. And I prefer my job stay in a box for the most part because I have lots of other things in my life.
Thanks for the response.
"Hey, you already make great money doing what you love and are good at. The next step is to make more money while having a much higher workload full of stuff you hate and are bad at."
...Like, what?
It makes sense if you're a janitor or a paper pusher or something. Now you manage janitors without getting dirty; it's mostly upsides. But with our bizarre, quasi-"artist" attachment to the work, it's an almost tragic trajectory.
I went back to IC - the politics and managerial stuff just wasn't as interesting as the technical stuff.
My q to everyone who has kept at it: did you continue up the career ladder into staff eng-type roles? They’re put on the IC ladder but get further away from programming. I’m still conflicted about that. I can see myself trying that for a few years then just dropping back to senior level.
I did realize recently that it is hard to give up programming when my whole professional career has been built around being seen as the person who programs things well.