[State of Code Evals] After SWE-bench, Code Clash & SOTA Coding Benchmarks recap — John Yang
Source
youtube.com
Author
Latent Space
Date
Why it matters
Maps the current family of coding benchmarks and where they differ, helping you choose evalA repeatable test for AI quality — a set of tasks plus scoring — used the way software teams use test suites, because model output is too variable to judge by eyeballing.Full definition → that reflect real AI agentAn AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.Full definition → performance.
Key takeaways · AI-distilled
John Yang says SWE-benchThe standard benchmark for AI coding agents: real GitHub issues from real repositories, scored by whether the agent's patch passes the project's own tests.Full definition → Multilingual spans about nine languages across roughly 40 repositories, part of a push in the follow-up benchmarks to diversify beyond the original set's heavy Django focus.
Yang describes CodeClash as replacing unit-test verification with tournaments: two or more models each maintain their own codebase, edit it every round, then the codebases are run against each other in an arena that decides which is better.
Per Yang, CodeClash's first arenas are existing programming games chosen for scientific purposes, and ongoing work aims to build arenas tied to economically valuable tasks, closer to the real-world utility of SWE-bench and Terminal-Bench.
Yang recalls a study that rewrote SWE-bench Verified issues to be impossible and checked whether models would admit they could not solve them; in his recollection the models mostly attempted the tasks and claimed success.
The host pushes back on benchmarks rewarding long autonomous runs, arguing real users underspecify tasks and want fast back-and-forth, which is hard to benchmarkA standard public test set for comparing AI models — the shared scoreboards behind every "model X beats model Y" claim.Full definition →; Yang partly agrees, pointing to his Stanford lab's human-AI collaboration focus.
Terms in this piece · Glossary
SWE-bench — The standard benchmark for AI coding agents: real GitHub issues from real repositories, scored by whether the agent's patch passes the project's own tests.
eval — A repeatable test for AI quality — a set of tasks plus scoring — used the way software teams use test suites, because model output is too variable to judge by eyeballing.
AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
benchmark — A standard public test set for comparing AI models — the shared scoreboards behind every "model X beats model Y" claim.