About
Exploring Solution Spaces, Keith Ray's blog on Software development and other topics.
Send comments to:
keithray@mac.com
| For Agile Training, eLearning, or Coaching contact: |
| Industrial Logic, Inc. |
| 866-540-8336 (toll free) |
| 510-540-8336 (Berkeley, California) |
| Links |
| xpminifaq |
| Résumé |
| “Adopting XP” Article 2002 (pdf) |
| “ Refactoring” Article 2006 |
| AYE Conference |
| Lucien W. Dupont |
| Elisabeth Hendrickson |
| Johanna Rothman's Managing Product Development |
| Brian Marick's Exploration Through Example |
| Esther Derby's Insights You Can Use |
| Laurent Bossavit's Incipient(thoughts) |
| Dale Emery's Conversations with Dale |
| Martin Fowler's Bliki |
| Creating Passionate Users |
Archives
Subscribe
RSS Exploring Solution Spaces XML
2007.Apr.04 Wed
If you don't pay down your Technical Debt as soon as it you incur it, ... it's like never paying down the balance on your credit cards. Soon you'll have so much interest and penalty debt on your credit cards that you can't pay them off at all. Technical Debt consists of refactorings and bug-fixes that don't get done (or get deferred), slowing down present and future development.
When a programming team says they can't make progress with the current software and that it needs to be rewritten "from the ground up", that's declaring Technical Bankruptcy.