> Once you learn that stack in your junior years, you are stuck on that path for the rest of your career.
That's not true while employed, since you can learn a new stack/tool/tech as part of a new project. People do this all the time, on spectrum from "choosing the right tool for the job" to "CV-driven development" (depending on how much you'll screw over subsequent maintainers).
I know many devs don't have the luxury of making big decisions for new projects; but there can still be opportunities to automate or improve some of your day-to-day tasks (e.g. scripts, aliases, sanity checkers to make sure you never do that thing again, etc.). For that sort of stuff you can use any technology you like, either as a quick, low-stakes way to learn something new, or an opportunity to use something you know from outside of work (admittedly this is more suited to using new languages; rather than e.g. a Web framework or server orchestration solution!). You can legitimately put that on your CV as a technology you've used commercially to solve problems, and that may be enough to get past HR filters. You can also share such things internally, to bolster your reputation as "someone who knows foo" (e.g. I was once given a task at work because there was an existing R package for what we needed, but nobody else knew R; whereas I once wrote a three line R script years ago!)
Unfortunately for this thread: that sort of tactic only works when in employment.
That's not true while employed, since you can learn a new stack/tool/tech as part of a new project. People do this all the time, on spectrum from "choosing the right tool for the job" to "CV-driven development" (depending on how much you'll screw over subsequent maintainers).
I know many devs don't have the luxury of making big decisions for new projects; but there can still be opportunities to automate or improve some of your day-to-day tasks (e.g. scripts, aliases, sanity checkers to make sure you never do that thing again, etc.). For that sort of stuff you can use any technology you like, either as a quick, low-stakes way to learn something new, or an opportunity to use something you know from outside of work (admittedly this is more suited to using new languages; rather than e.g. a Web framework or server orchestration solution!). You can legitimately put that on your CV as a technology you've used commercially to solve problems, and that may be enough to get past HR filters. You can also share such things internally, to bolster your reputation as "someone who knows foo" (e.g. I was once given a task at work because there was an existing R package for what we needed, but nobody else knew R; whereas I once wrote a three line R script years ago!)
Unfortunately for this thread: that sort of tactic only works when in employment.