Staying in the comfort zone means doing 5 times 1 year of experience. It’s safe, but you are taking a long term risk of becoming less relevant and end up reduci

Staying in the comfort zone means doing 5 times 1 year of experience. It’s safe, but you are taking a long term risk of becoming less relevant and end up reducing your options. This makes no sense to me. If you spend five years working on a tech stack that goes out of favor, then some will say you've wasted your time. Personally, I disagree, because experience is experience and what we do is learn, but good luck getting through an HR filter with that. This just seems like one of those "I'm the beneficiary of luck, now let me tell you how I credit myself for it" posts. My personal experience is that I've had the greatest growth when I was allowed to pursue what I'm interested in (e.g. coding styles, new libraries, new methods of structuring code such as functional vs OOP). When I get a meddling manager insisting that I do things some other way, I don't learn and grow nearly as much.