"It's always start over in a new stack." - I think you yourself have control over this, and may need to be ruthless. My career has been long, successful, OK

"It's always start over in a new stack." - I think you yourself have control over this, and may need to be ruthless. My career has been long, successful, OK not stress-free, but also not breaking point. Its been decently financially rewarded, some would say I could've earned much more but there-in lies stress and time famine. I'm content. I attribute this partly to vigilance about skillset. Find skills that are here to stay - Deep Linux, bash/zsh/whatever shell command line programming, Python, nowadays docker, AWS, devops, Go possibly worth a look. I shunned the MS stack - vendor lock-in and constantly being re-invented. I was wary of JS libraries - content flux and short shelf life. Be wary of obscure vendor specific stuff where that vendor can get bought out or change course. Tech with a big open source community is good long-term. And fun :). You may need to move jobs to get what you need. But I'd say, take ownership of skills, don't let people push you around, being forced to keep learning new stacks can lead to burn-out and impression of being weak performer. Don't let 'em do this to you. Even if you go to a new team with different tech, you can often find a way to use your base skills and not let them atrophy. Whenever I was on Windows I'd install Cygwin and do shell scripts instead of dos or powershell ;). you can do some tricks that solve problems quickly in weird ways that impresses people, I'm sure you know that. Good luck :)