What is Technical Debt
What you'll learn: How shortcuts and quick fixes in code create future costs that must be "paid back" with interest.
The Core Idea
Technical debt is a metaphor that compares software development shortcuts to financial debt. When you borrow money, you get immediate benefit but must pay it back later—often with interest. Similarly, when developers take shortcuts to deliver features faster (perhaps to meet a deadline or satisfy a stakeholder), they create code that's "good enough" now but will cost more time and effort to maintain or modify later.
Why Technical Debt Happens
Remember the Iron Triangle and Good-Fast-Cheap? When stakeholders demand "fast," something has to give. Sometimes the team chooses speed over code quality:
- Skipping proper documentation
- Copy-pasting code instead of creating reusable functions
- Ignoring best practices to hit a deadline
- Building workarounds instead of fixing root problems
This isn't always wrong! Just like financial debt can be strategic (taking a loan to start a business), technical debt can be intentional—getting a feature to market quickly might be worth the future cleanup cost.
The "Interest" Payment
The real problem is the interest: the longer technical debt sits in your codebase, the more expensive it becomes. That rushed code becomes harder to understand, harder to change, and more likely to break. What might take one hour to fix today could take five hours next month and twenty hours next year.
This connects directly to Maintenance Over Initial Development—most of a software system's life is spent being maintained, and technical debt makes maintenance increasingly painful and expensive.
Key Takeaway: Technical debt is the future cost created by today's shortcuts; like financial debt, it must eventually be repaid, and the longer you wait, the more "interest" you pay in harder maintenance and reduced agility.