Re:Ask HN: Are older devs more resistant to adopting new tech?
by dragonwriter on Monday January 20, 2020 @06:43PM
(#22103024)
There's certainly a correlation between age and several factors that contribute to the absence of neophilia, notably (but not exclusively):
(1) expertise/investment in existing tech platforms: why get into something where you'll be one of many with 1 year of experience where you are already on a platform where you've got 20?
(2) having seen the hyped products fizzle out quickly. Why get involved in something that may not ever have industrial demand materialize where you are already invested in a platform that is established and will have, even if it was abandoned for all new projects tomorrow, demand for expertise driven by legacy software for longer than the remainder of your working career.
(3) Fatigue with the whole cycle of learning the basics of yet-another-stack rather than deepening knowledge of established stacks, application domain, engineering/analytical/process mastery that isn't tech stack specific, etc.
I'm a 40+ dev who loves learning new things including tech stacks, but I absolutely don't view "learning new tech stacks" (especially really new ones rather than established but new-to-me ones) as anywhere close to the most career-useful use of time. Its a hobby that sometimes has nice career side-benefits.
OTOH, for a new dev some of this isn't just missing but positively inverted: a new tech stack is an opportunity that, if it takes off, for you to be in a position that while you'll still have to compete with people with more general experience, you won't have to compete with people with a decade or more stack-specific experience than you have, whereas with an established stack there is no way to avoid that.
(1) expertise/investment in existing tech platforms: why get into something where you'll be one of many with 1 year of experience where you are already on a platform where you've got 20?
(2) having seen the hyped products fizzle out quickly. Why get involved in something that may not ever have industrial demand materialize where you are already invested in a platform that is established and will have, even if it was abandoned for all new projects tomorrow, demand for expertise driven by legacy software for longer than the remainder of your working career.
(3) Fatigue with the whole cycle of learning the basics of yet-another-stack rather than deepening knowledge of established stacks, application domain, engineering/analytical/process mastery that isn't tech stack specific, etc.
I'm a 40+ dev who loves learning new things including tech stacks, but I absolutely don't view "learning new tech stacks" (especially really new ones rather than established but new-to-me ones) as anywhere close to the most career-useful use of time. Its a hobby that sometimes has nice career side-benefits.
OTOH, for a new dev some of this isn't just missing but positively inverted: a new tech stack is an opportunity that, if it takes off, for you to be in a position that while you'll still have to compete with people with more general experience, you won't have to compete with people with a decade or more stack-specific experience than you have, whereas with an established stack there is no way to avoid that.