I've been writing code professionally since 2001, and on an amateur basis since learning basic and machine language on my Commodore 64 in 1989. The thing that

I've been writing code professionally since 2001, and on an amateur basis since learning basic and machine language on my Commodore 64 in 1989. The thing that many younger devs don't (yet) get is that tech works in cycles. Today's hotness is yesterday's tried-and-true. As an example, Java (J2SE) came out in 1998 and my guess is - based on open positions on e.g. Stack[1] - that you'll still be able to write Java for decades. So for an old guy to adopt new tech: 1. I'd want there to be obvious benefits that outweigh the costs for the new approach. As an example, I'm not convinced FE frameworks are the best approach for CRUD apps. If you're building Trello and need crazy interactivity, sure. But you incur a bunch of cost vs. say Django / Rails / Laravel with intercooler or Stimulus sprinkled into interactive pages. And what's the huge cost for? Skipping a few page refreshes? 2. I'd want tech to be mature enough that I feel good it's going to be around and therefore is worth investing in. As you get older your time becomes more valuable as you tend to take on other obligations (kids, spouse). Hacking on new tech late at night or all weekend is less palatable or possible than it used to be. Curious to hear what others think though. 1- As of writing there are 425 jobs that mention Java (https://stackoverflow.com/jobs?q=java https://stackoverflow.com/jobs?q=java). Surprisingly there are only 341 that mention React (https://stackoverflow.com/jobs?q=react https://stackoverflow.com/jobs?q=react).