Be curious and read the docs. At some point everything will become similar.
Things I do (it might not work for everybody)
- Watch conferences talks Coding Tech, ConfFreaks, ElixirConf even CppConf
- Read issue tracker of projects I like: Typescript, webpack, node.js
- Side projects and open source contributions
- Hacker News and email subscriptions: React Status, Dev.to
I do not find that I need to keep up with everything. I choose a tech stack, work it for a few years, and then go out and catch up on what is new. Unless you are doing some kind of consulting where you need to be building greenfield apps with the bleeding edge every month, keeping up isn't as critical as it might seem.
I focus at least one third of my learning time on things that dont change, such as principles behind Hickey’s Simple Made Easy, Hamming’s You & Your Research, Brooks’ Mythical Man Month, functional programming, and technical things like SQL, shell.
New tech is a often a container around those, making it easy to grasp it.
Also, new tech also dont have such community & ecosystem around it as older tech, so I keep it on the radar, but dont use in production immediately. Focusing on boring technology, with a spark of novelty where needed.
I focus on technologies which have seen a steady growth over the years, like FreeBSD. The benefit is that the knowledge you obtain tends to stay relevant for a long time.
Easy. Just ignore it. Tech, like anything else, is just a bunch of cycles that keep on repeating themselves. The same principles are being constantly re-invented and re-discovered over and over again.
YAGNI and KISS.
None of it is necessary. A 20 year old LAMP stack with a few hosts will get your business to $1 billion dollars ARR. People pushing the complexity are trying to fleece big corporations and executives that don't know better.