Asked about Error analysis: read traces before you write evals
Why note only the first failure in a trace?
An answer that works
Later failures are often consequences of the first. If retrieval fetched the wrong document, the wrong answer that follows is not a separate problem. Counting both inflates the downstream failure and hides where the fix belongs.
Reading an answer is not being able to give one. The section that teaches this is Error analysis: read traces before you write evals, 6 hours of Evaluation.
Learn this properlyAlso asked about Evaluation
What is an eval?Why can you not just use unit tests?How would you start evaluating an existing feature with no evals?You join a team with an LLM feature and no evals. What do you do in the first week?Why binary judges rather than a one to five scale?Where do eval cases come from?Why split an eval set into train and test?How big should an eval set be?
All 24 questions on Evaluation