I agree with this but more so the DIY part. I usually _do_ have dependencies in my projects, a handful of important frameworks but avoid the utility libraries

I agree with this but more so the DIY part. I usually _do_ have dependencies in my projects, a handful of important frameworks but avoid the utility libraries as they have way too much surface area and its easy to roll them myself. But this is a deeply unpopular opinion in just about every company I've worked at. To go into more detail: for a custom built web app I might use nextjs, react, express, passport, prisma, and even some others. Sounds like I'm using a lot of dependencies right? I kind of regret using prisma, and maybe I can avoid using react / nextjs in the future. But I will handroll minor data manipulation needs, or requirements for 'fake' data, tests, etc. My experience at work is that the exact same app at a big company would be slower, and would have about four times as many dependencies, a complicated monorepo, and more. And trying to stop it is utterly futile.