Did Your Prompt Change Help? Prove It with an Eval
A model upgrade can change behaviour with no error. What an eval is, the three graders, the held-out slice, and how evals make upgrades routine.
12 posts
A model upgrade can change behaviour with no error. What an eval is, the three graders, the held-out slice, and how evals make upgrades routine.
Tool use and the agent loop in eleven lines of Python, the four changes that harden it, and when one loop stops being enough.
A chat prompt moved into code goes flat, forgets and fails with 400s. Send the history, write the system prompt, set effort and a schema, and read the stop reason first.
One line in an issue can make an agent send your secrets out, and a long session bills the same conversation many times. Break one leg of the lethal trifecta, make secrets unreadable, and clear context between tasks.
AI-generated code fails in ways that look fine, and people rate it higher than it deserves. How to prove a test can fail by breaking the code, what to read in a diff, and which decisions stay with people.
A brief written like a ticket, a check the agent can run, a plan you approve before code, and fences set in configuration. When it goes wrong, name the pattern and change what it sees.
If you type the same thing in two chats, it belongs in the repo. What earns a line in a rules file, a filled-in AGENTS.md, and a shared prompt library whose review prompt stops hiding real bugs.