Technical Debt and the Cost of the Next Change
A shortcut taken today is borrowed time, and the interest is paid by everyone who touches that code afterwards. Some debt is worth taking deliberately; the failure is taking it without recording it or planning when it gets repaid.
What a learner can do afterwards
- Identify a shortcut in a codebase and estimate what it costs per change
- Argue for taking on a piece of debt deliberately, with the repayment named
- Distinguish debt from code that is merely old and still fine
1 · Read
A shortcut today is borrowed time. Like a loan, it has a principal, the cleanup you skipped, and interest, the extra cost on every later change. Each future change pays part interest and part principal until the debt is gone.
You hard-code delivery zones to ship on time. Every new zone now needs a code edit plus testing, which is the interest. The principal is the afternoon needed to move zones into a table.
Some debt is worth taking on purpose, when shipping now matters more than clean code. The deal must name the repayment: what gets cleaned and when. Without a date, interest keeps compounding and nobody repays it.
Old code is not debt if it still reads well and costs nothing extra per change. Call it debt only when you can point at the extra cost each change pays.
Name the shortcut, price its interest per change, schedule the principal, and leave old code that costs nothing alone.
2 · Watch
Take it off screen
Where it sits
8 questions wait behind this lesson, each with its answer explained. Every answer feeds the sky: stars light as they are learned, and dim when it is time to come back.