Essay · About a 10 minute read

Technical Debt

Martin Fowler · martinfowler.com Free Intermediate

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.

• Technical debt is not about ugly code, it is about the extra time every future change costs you.
• A reviewer prioritizes cruft in frequently changed areas, and often leaves stable messy code alone.
• The deliberate versus reckless, prudent versus inadvertent quadrant helps you judge how worried to actually be.