It's a case of weighting the benefits and asking yourself when you're falling in the "not invented here syndrome". Testable and tested code are better than writing a code you'd have to implement all this again, even if it's a simple string validator and you need or intend to use more than one of those. On the other hand, some validators are so simple and straightforward with specific algorithms behind it, that it's better to write it yourself and leave behind the weight of running another scan for updates, vulnerability, compatibility, licenses and installation of other 20 string validators you will never use.
5 days ago | 1
Amigoscode
Ever feel like your code is a simple, elegant cat behind the wheel…
…until you look at the dependencies holding it all together? 🐱📦
This meme hits a little too close to home.
We often think our projects are lightweight, but every package, framework, and library adds complexity (and risk).
👉 A few reminders for all developers:
- Audit dependencies regularly.
- Don’t install a package for a one-liner you can write yourself.
- Keep things simple where possible. Future you will thank you.
At the end of the day, the less baggage your code has, the smoother the ride 🚀
How do you keep dependency bloat under control?
5 days ago | [YT] | 66