this site needs a good modern browser
please go install one and come back.
please go install one and come back.
interest rate: %
| transaction | credit* | debit* | balance* |
|
|
|||
|
interest |
|||
|
interest |
|||
|
interest |
|||
|
interest |
|||
|
pay off some tech debt |
100 |
||
|
interest |
|||
|
interest |
|||
|
interest |
total interest we had to pay during the life of the software:
now pretend each point of interest we pay on tech debt equates to a day of extra work: months of additional cost over the life of the system
* units of technical debt, you could think of this in terms of technical debt dollars
things a development team might hear:
"Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt. Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. Although it costs to pay down the principal, we gain by reduced interest payments in the future." - Martin Fowler