I write about the moments when two things that should have matched did not — a doc and the code under it, a green test run and a broken feature, one architecture and five languages that each read it differently. Backend work, mostly in TypeScript, Go, Java, Kotlin, and Python.
A forecast is only worth reading if you can see where it missed. Three rules make that possible: write the forecast down three months before the answer arrives and never edit it, commit the scoring rules before the first score exists, and leave a cell blank when the sample is too small to say anything.
Design notes for running several coding agents on one machine without stepping on each other: a container per agent so the unit of isolation is also the unit of cleanup, agent-to-agent messages over the network, nested containers only when needed, credentials that are shared without being baked in, and a cgroup-only alternative tested with systemd.
Every page passed a word-count check and had a distinct title, URL, and numbers. Slightly under half of all text on the site still existed on more than one page. The fifteen-line measurement that found it, and three structurally different ways a page duplicates its neighbour without anyone deciding it should.
A 3D conquest game in the browser. Bots fill both armies; you take the capture points on foot or in an attack helicopter (coalition side only for now). One map and a quick conquest mode so far, with no server and no sign-up.
This blog uses cookies for visit measurement (Google Analytics) and ads (Google AdSense). Declining hides the ad slots only; the measurement and ad scripts still load. See the privacy policy.