Earlier quoted context omitted.
One problem with ageism and youth bias in the industry is that we are still heavily populated with devs more interested in hopping on the latest framework they heard about at a conference than in actually solving users problems. The amount of "how do I justify a rewrite because our tech stack is bad" posts you see in your typical reddit/etc programmer forum would remind you of this.
> devs more interested in hopping on the latest framework they heard about at a conference than in actually solving users problems. The amount of "how do I justify a rewrite because our tech stack is bad" posts you see in your typical reddit/etc programmer forum would remind you of this. These are old complaints. My dad worked in the tech industry since the pre-Mosaic days, and even then you'd hear the same arguments…
Not every tech is the new Spring, OOP, etc.
Not every project benefits from being immediately migrated to the new thing.
Once you've been through a few train wreck "get on the latest thing" projects, you see the benefit of actually delivering to users, regardless of whether the tech is bleeding or trailing edge.
If you are a small tech org, the benefit of being able to hire a team of people who have SUCCESSFULLY delivered with TechX (which is 3-10 years old) can outweigh jumping onto the latest thing.