[cratermoon]

Except that technical debt is not about writing bad code, and the author of this article gets it completely wrong.

"The metaphor of debt is sometimes used to justify neglecting internal quality... Teams who do this end up maxing out all their credit cards, but still delivering later than they would have done had they put the effort into higher internal quality."[1]

"the whole debt metaphor, let's say, the ability to pay back debt, and make the debt metaphor work for your advantage depends upon your writing code that is clean enough to be able to refactor as you come to understand your problem"[2]

"write the best code possible given a partial understanding of the problem so later when you do understand it better you improve the solution"[3]

1. https://martinfowler.com/bliki/TechnicalDebt.html

2. http://wiki.c2.com/?WardExplainsDebtMetaphor

3. https://www.youtube.com/watch?v=pqeJFYwnkjE