Asked about Grading: code first, judges second
How do you evaluate something subjective like summary quality?
An answer that works
Use deterministic checks for everything checkable first. For what remains, break 'quality' into specific failure modes you have seen, such as unsupported claims or missing the main point, and write a pass or fail judge for each. Validate each judge against your own labels and report how well it catches failures alongside the score.
Reading an answer is not being able to give one. The section that teaches this is Grading: code first, judges second, 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 note only the first failure in a trace?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?
All 24 questions on Evaluation