My taste and the automated benchmark disagreed almost completely
The speaker discusses discrepancies between their subjective evaluation of model performance and automated benchmark results, noting that different judges (Opus, 4A, 5.5) show varying levels of generosity and bias. They conclude that personal judgment matters significantly and plan to incorporate more subjective taste into evaluation metrics while retiring saturated benchmark tasks.
Summary
The speaker describes an evaluation process where multiple language models served as judges to assess other models' outputs. They tested models including Opus, Claude 4A, and GPT 5.5, with particular focus on whether judges showed inherent bias toward themselves. A key finding was that GPT 5.5 emerged as the toughest judge despite being evaluated, and the speaker expresses a preference for using it as a judge. However, 5.5 judged itself more harshly than other judges evaluated it, suggesting some self-critical bias. Overall, the judges showed general agreement but tended toward generosity in their assessments. To balance these tendencies, the speaker implemented a double-bench approach with multiple judges. The speaker reflects that their personal taste diverged significantly from what the metrics indicated, leading to the conclusion that subjective evaluation ('vibe checks') shouldn't be dismissed. As a result, they plan to encode more of their personal taste directly into the judgment framework. Additionally, they identify that certain benchmark tasks have become saturated—specifically mentioning agentic bug tracking—where all models perform comparably well, making these tasks poor discriminators for evaluation purposes.
Key Insights
- GPT 5.5 was consistently the toughest judge across evaluations, even though it judged itself lower than other judges evaluated it
- Multiple judges show overall agreement but demonstrate a systematic tendency toward generosity in their assessments
- The speaker's personal taste and subjective evaluation diverged significantly from what automated metrics indicated
- Model performance depends on the specific task and how well a model's strengths fit that particular task type
- Saturated tasks like agentic bug tracking don't function as effective benchmarks because all evaluated models perform comparably well on them
Topics
Transcript
[0:00] We had a model as a judge, and so we had Opus 4A and 5.5 judge itself. I had the benchmark check if there was any inherent bias, like did Opus like 5.5 better? I've consistently seen GPT 5.5 be the toughest judge, and so I actually prefer a 5.5 judge, but it judged itself lower than the other judge did. The judges overall agree, but they were overall generous, and sort of balancing these two judges is exactly why we ran [0:30] this double bench. Takeaways, the model's going to depend on the job and the strength of the model fit by task. I would say my taste actually matters, so maybe those vibe checks are not bad,…
Full transcript available for MurmurCast members
Sign Up to AccessMore from How I AI
Jev mapped voice to color over the weekend
Jev built a real-time application that maps voice input to colors and emotions using OpenAI's real-time voice API, Java, and a quotes API. The system analyzes emotional tone and returns corresponding colors and relevant quotes in real time.
Jev: 8 real use cases this fast, cheap model
Claire Val and returning guest John Lindquist discuss Jev, a fast and cost-effective decision model from Type Safe AI, exploring eight real-world use cases including task management, data reconciliation, real-time routing, and agent coordination. They contrast Jev's structured decision-making approach with traditional LLMs, emphasizing how its speed and affordability unlock previously impractical applications.
Jev analyzed 1,700 PRs for 9 cents
A developer used AI (Gemini) to analyze 1,700 pull requests in 2 minutes for just 9 cents, extracting work allocation data across initiatives. This demonstrates how AI can help CTOs and CEOs quantify what percentage of engineering effort goes toward different products or projects.
Jev clusters your data for precise AI actions
Jev is a tool that enables precise AI actions by allowing users to organize large bodies of information through tagging, categorization, clustering, and filtering. The system applies targeted AI operations to specific data clusters, with practical applications including error severity sorting and intelligent email processing.
I tried Muse, Meta's new AI agent (meet Slime 🦖)
The speaker reviews Muse, Meta's new AI agent, highlighting its ability to perform browser-based tasks, connect to multiple data sources, and help users achieve personal goals through an approachable interface. Key features include connectors to email/calendar/health data, idea suggestions, artifact creation, and customizable avatars.