4 ms·
While I agree that if you think it'll just take an afternoon, for the sake of this article it had better! But conceding that charitable assumption to the artic
by kjeetgill 6y ago
While I agree that if you think it'll just take an afternoon, for the sake of this article it had better!
But conceding that charitable assumption to the article, I agree with its basic premise: dependencies cost a lot of time in diffuse, non-codey ways.
There are AAA dependencies you pull into every project, but most other dependencies require a good degree of due diligence, evaluation, risk, and their own long-term maintainance.
Its not that it always tips the scales all the way to 'roll your own', but
I think the cost of new dependencies is underrated.
- greyhair 6y agoBut that analysis is part of the design process on the front end. You don't just 'take' libraries or utilities without evaluating them. And you don't just write bespoke libraries without thinking about the APIs. So do your upfront work, by all means. It isn't an all or nothing decision.