A useful metaphor — and an often misunderstood one
Technical debt is one of those terms that gets used a lot, often loosely.
The original metaphor is precise. Debt is something you take on now to get speed, knowing you’ll pay interest until you settle it. Technical debt works the same way. You take a shortcut — write code faster than ideal, use a temporary solution, skip a piece of architecture — and you get something done quickly. In exchange, the codebase becomes a little harder to work with going forward.
Done well, technical debt is useful. You ship faster. You learn what’s worth investing in. You pay back the debt later, on parts of the code that have proven they’ll stick around.
Done badly, technical debt becomes a quiet anchor. The team slows down. Bugs multiply. Every new feature t...
