What an eval suite actually catches (and the three things it never will)
A 240-case eval suite for a ticket summarizer, a cheaper model swap, and an honest accounting of which failures the suite caught and which reached users.
No launch coverage, no leaderboards. Essays, postmortems and interviews about what happens after a model meets real users, real budgets and real Monday mornings.
In brief
A 240-case eval suite for a ticket summarizer, a cheaper model swap, and an honest accounting of which failures the suite caught and which reached users.
A design lead on why her team stopped chasing accuracy alone, the edit-rate metric they track instead, and the small interface changes that halved complaints.
Editors' picks
AgentsAn agent that is right 97% of the time still makes dozens of wrong moves a day. Reversibility, not accuracy, makes that tolerable. An argument, with a pattern.
Over six weeks an internal help assistant got quietly worse with no model or prompt change. The causes were all in the retrieval layer, and all preventable.
Model cards are marketing and documentation at once. A practical checklist for separating the claims you can rely on from the ones you need to test yourself.
We ran 3B, 7B and 14B open-weight models on two ordinary laptops to extract invoice fields. Speed, accuracy, memory and battery, measured rather than guessed.
One essay every other Thursday on evals, retrieval, agents, latency or cost, with the arithmetic shown and the code attached.
Free · No sponsored posts · 18,400 readers