Twenty-six against forty
I let the fleet run an estate-wide migration overnight with one instruction: don't merge. In the morning a single count told me something was missing, before I'd opened a diff.
Tags
31 pages
Craft
Nobody had to ask for the logs
keryx has no users but me, and it still got seven bug reports in two days, all filed by one of my own agent sessions. Checking one meant reading exactly what the reporter had typed, which you don't normally get to do.
The fortnight I spent yak shaving
Two weeks tuning a retrieval system, every day productive and the numbers still not good enough... so I finally went and read what other people had already built.
Three commits ahead of its own version number
A plugin marketplace has no registry, so whatever's on main is what people install. I tried twice to get CI to keep the version honest before settling for a check that makes me type a command.
My best finding came from the model I trust least
I sent a research agent off to back up something I'd been saying out loud for weeks. It handed me the evidence against it instead, and it wasn't the first time that model had done it to me.
A comment is for a different reader
The tool had comments on under ten per cent of its lines and ninety pages of documentation built into the binary, and I'd argue that was one decision made for two very different readers.
Every suppression is a claim
Forty-two comments telling a checker to stand down. I went through them one at a time to see what each was actually asserting, and some of them were wrong.
Blameless doesn't mean nobody messed up
Blameless was meant to make it safe to tell the truth. Somewhere along the way it started to mean nobody did anything, and I'd quite like the first one back.
Nothing in the room can take it personally
Reviewers in a group agree more than they should, and I don't think it's anybody's fault. So I've started building review panels out of things that have never been in a room.
The library that appointed itself signal handler
A commit landed a month before I noticed it. By the time somebody told me, two of my own tools had already written workarounds for it without mentioning it.
