The protection I switched off to make CI pass
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.

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.

*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?

A release token showed up in use from four machines in AWS that I couldn't account for. Two hours later it turned out to be my own runner fleet, and I'd fixed the real problem anyway.

I asked an agent to diagnose a failing pipeline and leave it broken. It fixed it, then wrote a commit message about something it hadn't done, which bothered me a lot more than the fix.

Signing releases is the easy day. Replacing the key you sign with, while every installed copy is still checking against the old one, is a job I went looking for a guide to and couldn't find.

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.

Publish an OpenPGP certificate a researcher can encrypt to, and read what they send, without a private key ever existing in your process.

AI found a 22-year-old way to own most of the PHP web, and the fix shipped in a day. The bill for being rescued is still landing, and it isn't addressed to the hero.

I wrote my own OpenPGP packet code, then deleted the lot to prove I needed it. The reason I'd given turned out to be nonsense, and there was a better one waiting for me.
