4 ms·

Another way to bridge the communication gap is to introduce the notion of "engineering debt" aka "technical debt". If you can quantify the day-to-day impact ("t

by DenisM 17y ago

Another way to bridge the communication gap is to introduce the notion of "engineering debt" aka "technical debt". If you can quantify the day-to-day impact ("the interest payments"), amount of work it would take to fix it ("the principal") and the ongoing accumulation of crap ("the negative ammortization loan") you will be loved by both engineers and managers.

Tichy 17y ago
Still, there is the 90% rule that code can not overcome, either: 90% of everything is crap (except crap, 100% of crap is crap).
- DenisM 17y ago
  That's just engineering nihilism speaking. :-) Surely the code you wrote last week was not 90% crap?
  - Tichy 17y ago
    To be honest I assume that most of my code is crap. Otherwise I would never get started because I would be stuck with architecting for the next 2000 years.