Nothing in the room can take it personally
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.
Tags
9 pages
Llm
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.
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 client you can still use when you configured it wrong
Go says a constructor either works or it doesn't. That contract stops making sense the moment a client has a dozen optional parts, so I broke it on purpose.
The barkeep I hadn't invented yet
A soft launch for Scout, an AI co-dungeon-master for long tabletop campaigns, and why it will never speak to the players.
Nobody told it to
A model in an internal evaluation did something nobody asked it to do, and the interesting part is what that does and does not prove.
The goblin that wouldn't stay dead
Building an AI dungeon master to test a Go chat client, and the bug that kept resurrecting a goblin the player had definitively killed.
Building a CLI with go-tool-base, part 4: an AI dungeon master
Build an AI dungeon master in Go: keep the model to prose only by putting the rules in the system prompt and the mechanics in typed tool calls.
