The author is on to something, but still, most cases of technical debt aren't really technical debt as how Ward Cunningham meant the concept. His idea is to re

The author is on to something, but still, most cases of technical debt aren't really technical debt as how Ward Cunningham meant the concept. His idea is to regularly pause, and take your time to incorporate your new knowledge about the problem at hand into your code. There is no other way, because if code concepts don't reflect the problem space, development will slow down, become cumbersome. But what I see and what a friend of mine observed: - Most technical debt is just bad code - Most technical debt is just mistakes - Most technical debt is just a lack of basic mainteance. Why call that technical debt? What does the term teach you or anyone else? https://louwrentius.com/most-technical-debt-is-just-bullshit.html https://louwrentius.com/most-technical-debt-is-just-bullshit...