After coming out of an interview with a dev manager, I left thinking about his emphasis on employment duration. For context, his network engineer has been on the team for 11 years. As developers we are responsible for our own learning (i.e. side projects, new languages etc.). However in a market where real world production experience takes weight and technology expands faster than most business adoption rates of new technology, how is a developer to remain relevant and highly employable if they are working in a stack that becomes outdated simply so they can say on paper they spent X years > 4 working for xyz corp?
*While this question my sound similar to questions pertaining to job hopping appearance on a resume, its focused more on how to balance between relevance and employment duration than fixing a job hopping appearance after the fact.