• A concept in software development that reflects the implied cost of additional rework caused by choosing an easy (limited) solution now, instead of using a better approach that would take longer. As with monetary debt, if technical debt is not repaid, it can accumulate “interest,” making it harder to implement changes. Unaddressed technical debt increases software entropy. Technical debt is not necessarily a bad thing, and sometimes (e.g., as a proof of concept) is required to move projects forward. On the other hand, the “technical debt” metaphor may minimize impact and result in insufficient prioritization of the necessary work to correct it. ← Wikipedia

1. Previous term: Technical Architecture Group
2. Next term: Technical key
3. Random term: 80