THESIS / 001
Technical debt has a compound interest rate. Pay structural debt first.
01
ARCHITECTURAL COMPOUNDING
Shortcuts taken at the database model level force every downstream service, API endpoint, and UI component to implement workarounds.
01SHORTCUT
→02WORKAROUND
→03DEPENDENCY
→04COMPOUNDCOST
→05SYSTEMRIGIDITY
FIG. 01 / COMPOUND SYSTEM RIGIDITY
FINAL VENTURE / ENGINEERING NOTESHow database shortcuts create cascading requirements for surrounding systems.
02
THE TAXONOMY OF TECHNICAL DEBT
Surface debt — messy code, missing tests, inconsistent naming — is cheap to fix and rarely compounds.
DEBT CLASSIFICATION
SURFACECan this be fixed by one engineer in one sprint?
STRUCTURALDoes this affect how other systems interact?
ARCHITECTURALDoes this constrain what the product can become?
03
WHEN DEFERRAL IS THE RIGHT DECISION
Not every shortcut is wrong. Startups must ship to learn. The question is what to defer and what to get right from the start.
DEFER POLISH. NEVER DEFER BOUNDARIES.
ENGINEERING NOTE / 004
The cost of a technical shortcut is not the time saved today.
It is the time required to reverse the decision multiplied by the number of systems that now depend on it.