"When you focus on mastering frameworks, you end up chasing trends. In recent years, there’s been a rush to learn new tools rather than mastering the underlying principles of coding and problem-solving. This approach runs contrary to the spirit of innovation. A competent craftsman isn’t defined by their tools but by their skill, creativity, and understanding of materials."
(Original title: Framework overload: when convenience dulls innovation in software development)
https://prahladyeri.github.io/blog/2024/10/framework-overload.html
@tante This is exactly the same thing I've noticed as well (this phenomenon has pretty much taken over the JS world since the startups rolled in during a hype cycle), but frustratingly we now seem to be looping back to "don't use other people's code ever" instead of people actually critically asking themselves whether maybe it's the *type* of dependency that's the problem 🙁
