Technical debt is a well-documented endemic problem within software development.
However, to understand why high levels of technical debt exist within most organisations, we need to change the way we think about this problem. We already understand more than enough about our software development processes and the various causes and types of technical debt involved in the trade-off between functionality and technical debt.
What we do not understand well, and need to understand better, is how our mind makes that trade-off decision and why technical debt fares so badly in that trade-off.
- The causes of technical debt are well understood.
- However, the levels of technical debt are uncomfortably high
- To change the levels of technical debt, we need to understand how our mind makes trade-off decisions.