What happens when an AI burns out
A Claude session ran for two days, stopped listening and got my hand-written code backwards. So I took it off the job, and asked for a proper handover first.
Categories
84 pages
go-tool-base
The underpinnings for any Go application that ships as a binary: command-line tools to start with, and (as more than half of what is built on it now proves) long-running services and local web UIs too. It standardises the boilerplate and wiring you end up writing in every Go project, and puts config, logging, self-update, a DI container and the rest straight at your fingertips. Highly opinionated, and it makes some calls people will disagree with, but it works, and it works really well. The CLI it ships with is a big part of that: keeping a Go app built, updated and maintained becomes almost trivial.
The bill for fifty-one modules
Change one line in the tls module and you've signed up for twelve releases. That's not a bug in the architecture, that's the architecture.
The extraction playbook only got real when chat left
I wrote the process document before doing the hard one. Then the hard one went through it and rewrote a step.
Prove the bug before you fix it
A model handed a bug will hand you back a plausible fix and a green test suite in about a minute. That tells you almost nothing.
The packages that didn't want to leave
Everyone writes up the modules that came out. The decisions that mattered were the four packages I decided to leave exactly where they were.
I graded every package for how badly it wants to leave
Twenty-seven packages, four marks each, out of ten. The interesting column wasn't the one I expected, and one row explained the whole programme.
The day a script needs changing everywhere
Eleven variants of one shell script, on hundreds of laptops, launching pods into production. The language was never the problem, and it wasn't the fix either.
Config is a border, not a chain
I built a boundary so I wouldn't have to move my config package. Then I moved it anyway, and the boundary is the only reason that didn't hurt.
An agent is a loop with real tools and a fence
An agent is a model in a loop with tools it can really call and results it can really see. Taking the ReAct pattern apart in go-tool-base.
Publish your key where the platform can't touch it
If the platform hosting your code also hands out the key that verifies it, the signature proves nothing. Where to publish a public key instead.
