The stoichiometry of technical debt

In chemistry, an unbalanced equation isn't a style problem — it's a physical impossibility. Atoms don't disappear because your math was lazy. Technical debt is the same phenomenon with slower consequences and worse tooling for noticing.

The chemistry of compounding

In the lab, reactions balance: what goes in must come out, transformed. In software, shortcuts also balance — the complexity you skip today reappears somewhere. Skip the migration script; meet the mystery state next quarter. Skip the validation; greet the corrupt data. The universe of a system is conservative like a chemical equation: nothing is truly deleted, only transformed and relocated.

Catalysts and hotspots. Chemistry taught me that small amounts of some substances change everything about reaction speed. Codebases have the same: one untyped boundary, one untested money path, one load-bearing regex. A tiny amount of negligence at a catalytic point alters the whole system's rate of decay. Find the catalysts; the rest of the debt is slow sand.

Buffer solutions. Pharmacy formulations resist pH swings through buffers — deliberate structure that absorbs shock. Software equivalents: queues, retries, circuit breakers, feature flags. Systems with buffers degrade gracefully; systems without them shatter on the first swing.

The habit this gave me

When I estimate a shortcut, I now ask the chemistry question: where does the unbalanced part go? Because it goes somewhere. It always goes somewhere — the skill is choosing where, and pricing it honestly.