Skip to content

Comment on Don't solve the solved problemsparent

Comments

It depends a lot on scale. If you're just throwing together a web app that isn't going to have crazy amounts of traffic or business then maybe a big messy dependency chain is ok. But every one of those dependencies is a risk and a liability, and the more valuable and significant your project becomes the more important it is to lock down risk and reduce liabilities. Which means tracking down and eliminating dependencies.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.