Technical Debt

Also called Tech Debt

The future cost of taking shortcuts in code or architecture today: quick fixes and skipped cleanup that make the next changes slower and riskier. Like financial debt, it accrues interest.

Why it matters

Some technical debt is smart, moving fast to learn beats perfect code nobody uses. The danger is letting it pile up silently until the product grinds to a halt, so it is a balance to manage consciously, not ignore.

For example

To hit a launch, the team hard-codes a hack that works for now; six months later that shortcut makes every new feature slower to build.

Worth your time

Technical Debt martinfowler.com · article This is the canonical explanation of what a reviewer actually means when they flag your inherited code as risky. Fowler frames messy code as debt you pay interest on: every future feature gets slower, which is the real cost you inherit from a rushed agency build. Read it to understand why a reviewer separates crufty-but-stable code (leave it) from cruft in code you touch often (fix it), so you can read a review report with judgment instead of panic. Open martinfowler.com →

Related terms

Minimum Viable Product Iteration Feature Flag

Go deeper

See how founders actually handle this on Building the product, part of the Starting Up hub.

eChai Partner Brands