Eval-driven development
1 creator use or recommend it
A development methodology for AI products where you write a failing evaluation (test) that reproduces a problem first, then write code to fix it, and prove the fix works by seeing the eval pass.
Recently discussed in
What creators say
"Always write a failing eval first, then write the code to fix it, prove that it works by seeing that the eval passes, and then seeing how the rest of the evals in your suite pass and then open up a PR. It's basically kind of the only way we work n..."
More from Eddie Kim →Keep exploring
Topics
About this data
- ✓48,000+ mentions extracted from real podcast transcripts
- ✓Every quote links to the source episode
- ✓Sponsored mentions are always labeled
- ✓Critical takes are shown, never filtered out