Blog
Twenty-three adapters went out against a core that had already moved on, and they all needed releasing again. So now something checks the engine's coupled on before the carriages leave.
I built a motorcycle navigation app for an audience of one, then rode it to the supermarket. Now it has a name, a beta and a need for testers.
I sent the bouncer home so a Go test could get in. It turned out he'd been turning away malware since the summer, and he wouldn't come back.
My generator could offer twenty-six config adapters, and the wizard's way of asking about them was all wrong. So the generator stopped asking, and the user tells the tool instead.
Building the labelled set everything else gets measured against, and the rule that made it usable: when you don't know, leave it blank.
*sshole let people log into accounts that can't be logged into, and when you pull it apart, each piece of the chain was someone fixing something. So what am I trusting when I patch?
For a week in July the whole estate's CI ran through three slots on one homelab VM, while a fleet of agents worked through twenty-one findings at once.
Something other than people is reading my docs now, and it quotes whatever sits at the top of the page. So the answer goes first and the explanation goes underneath.
I run a dozen agent sessions at once on the machine under my desk, and they all write to the same disk. So I built a crude tripwire to find out who was stepping on whose work.
One letter in a format string decides whether the check you wrote yesterday still works today. Here's the whole of Go's error chain, built up from that letter, with every output taken from a real run.