Technical debt and clean code

The more technical debt you take on, your disciplines need to be tighter. It would be best to do more testing, pairing, and refactoring.

Technical debt is not a license to make a mess.[¹]

A mess is the opposite of technical debt.

Technical Debt decisions are based on actual project constraints. They are risky, but they can be beneficial.

Technical Debt is a proposal for a solution when there’s not enough information about a problem.

Technical Debt is not a long-term solution but a way to explore a problem and gain real insights from direct customers.

The decision to make a mess is never rational, is always based on laziness and un-professionalism, and has no chance of paying off in the future.[¹]

Technical Debt is a strategic decision that is not an excuse not to follow the best-known practices in Software Engineering.

—

[¹]: Robert C. Martin (2009): A Mess is not a Technical Debt. — Clean Coder (https://sites.google.com/site/unclebobconsultingllc/a-mess-is-not-a-technical-debt)