I’m nearly 60, and I just learned React-Redux and am building a website using it. (Sweet architecture, btw — much nicer than Angular)

I don’t think there’s much problem staying employed if you stay current. The problem is that every one gives lip service to lifetime learning, but they don’t actually do it. Here are two not-typical pieces of advice on how to change that.

1. Set yourself up in situations where you must learn a new language, architecture, etc. If you don’t make it a must-do situation, you’ll put it off year by year until a decade later you’re out of date, or you’ll set it aside once you get frustrated. If at some point in the learning process you’re angry at yourself for having put yourself in a position where you couldn’t get out of learning all this stuff, you’re doing it about right. I like to volunteer to do projects using a new language/technology, or to teach a course in an area I know nothing about. Then I’m stuck, and I have to learn. Whatever works for you is fine as long as you have enough skin in the game that you can’t back off once you’ve committed.
2. You don’t understand the new language, architecture, etc. until you *like* it. If a new programming approach is popular, it’s for a reason, and not just because “kids these days have no judgment”. An example: I learned JS a while back, and had a hard time getting used to a loosely typed language, and to closures. I felt I’d finally arrived as a JS programmer when I went back to Java on a different project, and felt confined by the type system and lack of closures. I actually liked JS! Liking the new thing is a step beyond just understanding it. Don’t stop till you reach that point.