Why Long-Lived Codebases Need Patient Architecture
Cathedrals are built stone by stone — so are repos that last a decade.
[ essay ]
Short-term code optimizes for demo. Long-lived code optimizes for change cost.
Patient architecture invests in boundaries: modules with clear contracts, tests at seams, documentation for failure recovery. It accepts slower feature one if feature ten is cheaper.
Every commit adds stone. Ask whether this stone belongs in the wall or is rubble that future masons must remove.
Teams leave; commits stay. Build for the engineer who arrives in three years with no oral history.
