From (via Michael Tsai):

For a while, I’ve been using a different definition of Technical Debt. It helps teams frame their work in a way that highlights their choices and it can lead to better ones.


Technical Debt is the refactoring effort needed to add a feature non-invasively


But with their example -- granting it's a simplest case, "staged house" example -- no. No. Heavens no.

While they admit it a bit...

It’s easy to challenge this example. It borders on over-engineering.

Yes. It doesn't just border, it's over the line.

Over the line reply

Labels: ,