Whenever I explain that phpbotscout answers from the estate’s documentation, somebody asks why it doesn’t read the issues as well, and it’s a fair question. They’re right there, they’re full of questions shaped exactly …
I'd built this exact thing by hand, years ago, pixel perfect. So why was I sitting here shouting at a screen while a machine got it wrong three times?
go/mcp puts a Go CLI, HTTP service or gRPC service on the Model Context Protocol with three discovery tools instead of one per command, so a model carries a lantern rather than the whole catalogue.
I was a minute from filing a fix for a feature that had shipped the day before. The reason I had not noticed turned out to be a rule of my own, doing precisely what I told it to.
I built somebody else's idea into a working skill before nine and deleted it by ten. Not-invented-here is the accusation; here's the order I actually work in.
The requirements were done and I hadn't written a line of code. So I spent a day trying to talk myself out of the whole thing.
I asked nine agent sessions to stop compiling for forty minutes. What came back read like a team of colleagues, and I haven't worked out what to do about that.
A dozen agent sessions running at once is not a capacity problem. Working out which of them is stuck is, and the obvious way to find out is the wrong one.
I run a coding session per repository and they can't talk to each other. For a while the thing carrying messages between them was me, and I kept getting it wrong.
I put my working practice on a public shelf, and then took some of it back off again. Working out which half was the interesting part.
