The term Technical Debt was created by Ward Cunningham to describe the engineering trade-off’s that software developers and business stakeholders must often make in order to meet schedules and customer expectations.
I hope everybody among my readers is familiar with the concept of technical debt: If you do a quick hack to implement a feature it might be faster to implement in the short run, but you have to pay interest for the technical debt in the form of...
In a blog post on bad code and technical debt Steve Freeman described how Chris Matts came up with the metaphor of an unhedged call option for bad code. This post is being intensively discussed on Reddit and on Hacker News recently.
1. Types of Technical Debt An outline to use when discussing technical debt: Unintentional Intentional: (a) Short-term: Only if there is the commitment to schedule, prioritize, and fix soon (e.g., in the next sprint). (b) Long-term: Only if the commitment