The author is a little disingenuous with the post's title. As stated further within the post, he didn't stop learning frameworks. He just stopped learning frame

The author is a little disingenuous with the post's title. As stated further within the post, he didn't stop learning frameworks. He just stopped learning frameworks that he considers new and uses stuff like Spring. His rationale makes sense. > The Lindy effect: The future life expectancy of technology is proportional to its current age. Every extra period of survival implies a longer remaining life expectancy. I don't fully disagree with him that there's a strong chance of wasting time learning a bleeding edge framework that fades into the background after 2-4 years. Tapestry was a good example. However, where I disagree with the author is what he defines as a "new" framework. I don't feel that either React or Angular are new frameworks. Both are pretty established at this point. imo Rails and Django, as well as any framework based on express are probably pretty solid as well. The obvious danger of waiting too long to at least experiment with new technology is the risk of being left behind and being dumbfounded when new concepts become mainstream. This leads to not getting interviews as well. Why? It's more efficient for companies to vet people on standardized industry knowledge such as a framework. That said, Eduards Sizovs still has a point to keep in mind.