4 ms·
A lot of teams have decided avoiding all dependency management is better than mastering it. I'm trying to accept it, as another instance of "worse is better".
by erik_seaberg 8y ago
A lot of teams have decided avoiding all dependency management is better than mastering it. I'm trying to accept it, as another instance of "worse is better".
- ezrast 8y agoIn the general case, avoiding a problem is better than solving a problem. No code is better than no code.
- erik_seaberg 8y agoWhen A uses C, and B also uses C but another copy of a different version, that can create problems that would have been avoided by doing the planning work. Not only are you exposed to two sets of bugs in C (some of which are already fixed), but C may not be fully forward and backward compatible with its own output (especially in-process).