3 ms·
Yeah, good idea, but company architects should make a similar advice about NIH though. A dependency is a dependency, there may be tradeoffs between using third
by mrbungie 4y ago
Yeah, good idea, but company architects should make a similar advice about NIH though.
A dependency is a dependency, there may be tradeoffs between using third-party software and developing new in-house code, but using "Invented here" code does not vanish any kind of complexity away, it just manages it differently.
- travisgriggs 4y agoAgreed. That’s why I thought the footnote in the quote was brilliant. Guess I should’ve included that part as well: > [2] Ay, there’s the rub. I’m assuming competence. (If your company isn’t competent, well, you know what you need to do.)
- erik_seaberg 4y agoThe best third-party code has benefitted from industry-wide testing and fixes no single team could match. People we hire might come in already knowing it. Competence is partly in recognizing that a problem has been solved and is no longer a good use of time, at least until we have a plan to make an improvement so great to support the redundant maintenance forever.