So.. there's a lot to unpack here. There's a few ways to interpret the "hype-train" of mainstream development 1 - it's gonna solve all my problems 2 - everyo

So.. there's a lot to unpack here. There's a few ways to interpret the "hype-train" of mainstream development 1 - it's gonna solve all my problems 2 - everyone else is talking about it so I should learn it 3 - incremental ad-hoc solution to a real problem someone encountered, may or may not apply to me Many juniors are guilty of 1 & 2, few make it to realize that most of the time these lie in camp 3. There's a real use case for this, but you have to train your mind to not see it as a silver-bullet or worry about hype train. The difference between academia & industry is that academia tends to develop general solutions to problems few if any people encounter. The best of the industrial programmer will take the bits of academia & try to make our ad-hoc solutions slightly more general while staying practical. This is endless, and depending on your perspective its fascinating OR exhausting. To me its a bit of both, but with distance & the realization that I do not need to care about virtually any new tech, I usually lean to the fascinating side. As a language designer its humbling to see the milage people get out of many half-baked solutions in the JS ecosystem, and a sign that generality isn't the whole picture.