3 ms·
>> Of course in a Good team, needless dependencies would be weeded out in code reviews, and a Culture would evolve over time avoiding needless dependencies. He
by thaumasiotes 7y ago
>> Of course in a Good team, needless dependencies would be weeded out in code reviews, and a Culture would evolve over time avoiding needless dependencies.
Heh. This reminded me of a different story, which I remember vaguely enough that I'll paraphrase from memory:
> "The Excel team will never go for it. Their motto is 'Find the dependencies... and eliminate them.'"
> This probably explained why the Excel team had its own C compiler.
- mixmastamyk 7y agoSounds like Joel on Software.
- oblio 7y agohttps://www.joelonsoftware.com/2001/10/14/in-defense-of-not-invented-here-syndrome/ https://www.joelonsoftware.com/2001/10/14/in-defense-of-not-...
- hinkley 7y agoLike a lot of things in a Good Team, dependency curation requires a tempo. This will be done, and putting it off doesn't get you out of doing it.