Essay · About a 10 minute read · Starting Up
Technical Debt
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.
Martin Fowler · martinfowler.com · Essay · About a 10 minute read
The answers it serves3 answers
- We ship fast but our codebase is turning into a mess. How much should a two-person startup care about tech debt? Starting Up
- When is the right moment to stop iterating on the MVP and rebuild it properly, and how do I avoid the second-system rewrite trap? Starting Up
- When my technical hire and I disagree on the tech stack, whose call is it? Starting Up