I think it's naive to say that keeping up with the latest technology means just learning the new thing that came out. The key word in that last sentence is "learning" because it seems like anyone that feels overwhelmed by all the things they need to read up on is not really learning anything in the first place. I don't mean that to be condescending or as an experienced developer but I believe the bare minimum of having learned something means you can speak to its strengths and weaknesses.
Sadly the only thing that allows you to experience strengths/weaknesses is working without that newest thing and suffering the problem that the new thing addresses.
What I advocate for people starting out is focus on one language, one framework, and a couple crucial libraries for at least 6 months if not a year. The goal of this is to be able to comfortably communicate the strengths and weaknesses of what you know. Learn to be content not knowing the newest thing. You can definitely learn it on your extra time but only on your extra time. It's easy but unprofitable to barely know many things, it's way more difficult but better to know one thing well.
Great article Mark!