Three models vote on what happened
I ran one job past three AI providers and had them vote. The voting was the easy part. Deciding what counted as agreement was not.
Tags
36 pages
AI
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.
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 bot couldn't answer it. Neither could I.
I read the question my support bot had fluffed, gave the correct answer off the top of my head, and was wrong. The docs had fooled the person who wrote them.
The most tempting corpus in any repository
The issue tracker is full of answers, which is exactly why my support bot isn't allowed to quote it. An issue can point at the docs, but it never gets to be the answer.
A terrible lead to an AI junior
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?
Fifty-four tools before a word was typed
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.
Check the code you're reading is current
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.
Building it yourself is the third thing I try
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.
I went looking for the reason not to build it
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.
