What are you talking about? I'm 33 and I've thrown everything out and started over with new platforms, tools, libraries, and languages several times in my career so far. I haven't slowed down at all after getting married and having kids either... I've just gotten much better at recognizing dead ends early and not wasting time on stuff that doesn't matter.
This age trope seems to be from some early days when technology did move slower and people expected to spend their entire career working on the same technology. I've never had that expectation.
Anyone who thinks experience is worthless is an utter fool. My work hacking on an F# JavaScript compiler directly translated to doing massive CoW in-memory snapshots using immutable data structures in C#. My early work with SQL and transactions informed my approach to using atomic CMPEXCH to do optimistic in-memory commits, giving the entire app database-like MVCC transactional semantics.
All of that has been invaluable now that I do iOS development full time. Swift's approach to value types and mutability are natural fits to a wide range of things (like undo stacks and concurrent background processing while publishing consistent changes to the UI). Different platform, language, tools, etc but the experience was far from wasted. Hell, having done manual memory management back when iOS was an after-hours hobby project gives me the tools to find memory corruption bugs and diagnose crashes in an hour that some struggle with for days. Even within iOS there has been massive change and upheaval. There again, experience with generics in C# pays off.
Doing full stack development, writing JS libraries, wrangling with CSS... It's all been valuable experience.
This age trope seems to be from some early days when technology did move slower and people expected to spend their entire career working on the same technology. I've never had that expectation.
Anyone who thinks experience is worthless is an utter fool. My work hacking on an F# JavaScript compiler directly translated to doing massive CoW in-memory snapshots using immutable data structures in C#. My early work with SQL and transactions informed my approach to using atomic CMPEXCH to do optimistic in-memory commits, giving the entire app database-like MVCC transactional semantics.
All of that has been invaluable now that I do iOS development full time. Swift's approach to value types and mutability are natural fits to a wide range of things (like undo stacks and concurrent background processing while publishing consistent changes to the UI). Different platform, language, tools, etc but the experience was far from wasted. Hell, having done manual memory management back when iOS was an after-hours hobby project gives me the tools to find memory corruption bugs and diagnose crashes in an hour that some struggle with for days. Even within iOS there has been massive change and upheaval. There again, experience with generics in C# pays off.
Doing full stack development, writing JS libraries, wrangling with CSS... It's all been valuable experience.