Blog
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.
My R&D team's work only ever showed up in other people's numbers, so when delivery became the measure, they went. Making that work visible was my job.
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.
The engineering argument for paying down tech debt almost never won. What got it funded was a promise, and it tended to be my name on the promise.
Publish an OpenPGP certificate a researcher can encrypt to, and read what they send, without a private key ever existing in your process.
How big is a tool that does nothing? For go-tool-base it was 81 MB, and a comment in the code said it shouldn't have been.
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.
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.
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.
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.
go-tool-base
Soapbox
Campfire
Pioneering
signing
Orienteering
