Every development manager has faced the choices: Ship sooner? Squeeze in an extra feature? Test a little less to cut cost? Invest in infrastructure? Rewrite that problematic code? Virtually every development cycle goes through a similar set of tradeoffs multiple times in the course of getting code out the door. Every time a decision is made, the overall quality, maintainability, complexity, and stability of a software system goes up or down.
The Economics of Technical Debt
Posted September 30, 2010 | Leadership |
![](/sites/default/files/styles/square_thumbnail_180x180_/public/content-and-analysis/journals-and-reports/cutter-it-journal/sample/itj1010b/itj1010bfig01.gif?itok=hyflsYut)
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.