Explore / Build the product / Product management

Essay · About a 5 minute read · Starting Up

Technical Debt Quadrant

This is the canonical framing for exactly your question: not all messy code is the same. Fowler splits debt on two axes, whether you took it on deliberately or by accident, and whether the call was prudent or reckless. For a two-person team shipping fast, the useful cell is deliberate and prudent: you know you cut a corner, you thought about the payoff, and you plan to come back. That is a healthy place to be, and this piece gives you the language to tell it apart from the reckless kind that actually hurts.

Martin Fowler · martinfowler.com · Essay · About a 5 minute read

The answers it serves4 answers

  1. We ship fast but our codebase is turning into a mess. How much should a two-person startup care about tech debt? Starting Up
  2. Should we ship an ugly, half-working version now or wait until it feels good enough to be proud of? Starting Up
  3. 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
  4. How do I evaluate the code quality of a build I inherited from an agency? Starting Up