Backend engineer
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 recent finding
Half the Site Was a Copy of ItselfRead it
What I work with
I see technology as a tool for solving problems, and I choose it with operations and scale in mind.
Latest
A running record of lessons learned from design work and small experiments.
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.
Five Kubernetes anti-pattern checkers all assumed `---`-separated documents. Naming more than one resource in a single `kubectl get -o yaml` call wraps the result in `kind: List` instead, and every checker found zero resources to flag without a word, which looked identical to a clean pass.
Live
A first-person shooter drawn entirely in characters. It plays the 68 Freedoom maps and two levels of its own in the browser, with a keyboard or touch.
Live
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.
Live
Single-player multiplayer: raid bosses and battlegrounds played alone in the browser, with AI party members and no server.