2 ms·
Yup, you’re outsourcing your decisions in exchange for not doing the work. You have to understand your risks and needs. Your boring business systems that will
by Spooky23 4y ago
Yup, you’re outsourcing your decisions in exchange for not doing the work. You have to understand your risks and needs.
Your boring business systems that will live for 50 years need to have boring system level libraries or stuff you maintain. Your fast time to market or non-critical systems are optimized by speed and cost.
If your service depends on a bunch of downstream stuff, your processes need to support upgrade cycles. If you can’t keep up with that, you need to refactor.
- _jal 4y agoThere is pressure in our org to find ways to have fewer dependencies. Some of this is trivial, and a very good thing - stop using bullshit exercises in fragmentation like isEven. Some of it is very much not, and will apply pressure to find vendors who are willing to vet their own bundles of commonly used libs. There will be numerous second order effects of that, including the ghettoization of open source that isn't "QualStrike Approved(tm)".
- rowanG077 4y agoSystem level libraries are a huge risk. It makes updating much harder leading to many developers just foregoing updates unless absolutely necessary. Libraries your software uses should be decoupled as much as possible from system level libs.