If It Has to Happen, Don’t Put It in the Prompt
When agent instructions turn into all caps rules, the fix is often to move the requirement out of the prompt and into a workflow that can check it.
Building AI that actually works. Evaluation-driven development for engineering teams.
When agent instructions turn into all caps rules, the fix is often to move the requirement out of the prompt and into a workflow that can check it.
Logs tell you what happened. Annotations tell you what it meant, why it failed, and whether the fix helped.
One giant prompt can hide five separate jobs. Split the work so each part has a smaller contract and a failure you can actually name.
A bad RAG answer does not tell you whether retrieval failed, generation failed, or the product asked an impossible question. Split the blame before fixing anything.
If an AI answer goes sideways and you cannot see the prompt, model, latency, tokens, retrieved context, and failure path, you are debugging from vibes.
If every eval run emails a customer, updates production state, or fires a webhook, you do not have an eval harness. You have a hostage situation.
Agents get less spooky when they have named states, constrained transitions, and a record of how each decision moved the process forward.
Before blaming the model, inspect the chunks. Duplicate, empty, bloated, or low-signal chunks can wreck retrieval quietly.
When a multi-step AI run fails once and then refuses to fail again, replay beats superstition. Capture the calls, context, and intermediate state.
Agents should not get to delete files, send messages, spend money, publish content, or mutate production just because the next step looks obvious.
A citation is not proof just because the model printed a source name. Verify that the source exists and actually supports the claim.
If the rest of your app needs data, make the model return data. Do not make downstream code scrape nice-sounding paragraphs forever.
AI features get scary when prompts, logs, evals, schemas, fallbacks, and product code all live in the same pile. Give the weird part one stable interface so changes have a place to go.
Anthropic changed OpenClaw billing. We ran evals, tuned the bootstrap files, and GPT-5.4 got a lot better.
Any sufficiently complicated AI system contains an ad hoc, informally-specified, bug-ridden implementation of half of DSPy.
A streamlined system for AI evaluation that closes the gap between seeing problems and fixing them.
A Strategic Guide to Success
How Frigade Slashed Latency & Boosted User Helpfulness
The Enduring Value of Retrieval in the Era of Expanding Context Windows
An AI Maturity Model
A Practical Guide to Evaluation-Driven Improvement
It''s Not What You Think
A Story of Simplification
How LinkedIn''s Candidate Recommendation Project Changed My View of Data-Driven Development
A Leader''s Guide
The Hidden Cost of Missing Business Context
Why Working Harder Isn''t Working
How HealthRhythms built their mood score system