> Anxious and lazy dependency-first development culture ("you could never write that as well as some github rando")
I’ll die on this hill. You should pin your dependencies so you don’t get pwned, and then use dependencies for everything mildly complicated that isn’t core to your product.
I bet 90% of people reading this work somewhere that has built a model router in the last year.
I understand the sentiment. You work at a sparkling water company, and building a durable workflow engine is much more interesting than building a website.
But without that tech being your core product, maintaining and evolving it will lose priority. If it requires barely no maintenance, it’s even worse, because when it inevitably does, you don’t know if deploying a new version still works.
Use stuff that exists. If the dependencies don’t do what you need, fork them, and consider contributing a patch.
Tracking version changes and breaking api changes in dependencies and cves/vulnerabilities has a non zero cost, it’s simply dishonest to pretend it doesn’t.
Pinning deps only works if you subscribe to security release notifications from every one AND requires that they distribute those ~anywhere. Otherwise you’re missing patches.
And if you’re allowing patches via SemVer, you’re relying on authors using SemVer correctly, which they won’t. For example, the common practice of ~never having a 1.0 so the minor release is basically the major and the patch is effectively the minor.