Compound engineering, applied to a personal site
Five real pull requests from this site's own git history (a build, a review, a three-line fix, an extraction, and a compliance rule) show what compounding actually looks like when a fix from one PR gets applied automatically three PRs later without anyone repeating the instruction.
Five real pull requests from this site's own git history, in the order they landed. The first Thinking piece shipped with two fixes already caught in review, not filed as bugs a week later — a redundant link grid trimmed, a camera sway toned down from 3x to 1.1x. The second PR wasn't a build, it was a review that caught drift before it spread to the other nineteen pieces: bordered cards fighting the site's flat rule, a synthetic model standing in for the real one, no spine to the argument. Two PRs later a raw hex color and a text-shadow glow slipped into one specimen anyway, both banned by the site's own flat rule — three lines, caught and reverted before it set a precedent. The pattern under those fixes — the magazine grid, the optional stage number, the optional margin note — moved into a shared component every later piece imports rather than redefines slightly differently, including this one. Two PRs after that, a compliance pass found copy naming specific AI products by brand, a hard constraint since I can't publicly endorse a competitor's model while working at Google. The rule got written once. The very next batch, four pieces built by parallel agents, caught its own violation with zero new instructions. A rule that has to be re-explained every time isn't a rule. It's a request.