Engineering brief
Start with Vibes: The Counterintuitive First Step for Agent Evals
At a glance
- Relevance
- Practical value
- Warnings
- None
The YouTube Ads team found manual 'vibing' uncovers AI agent failure patterns faster than automated evals, preventing costly calibration churn. Agent traces, not pass/fail rates, expose hidden reasoning flaws—e.g., an agent stripping a legally required disclaimer.
Agent reliability in production depends on disciplined evals; this talk offers a hard-won, phased approach that reduces launch risk and costly rework.
Summary
The YouTube Ads team discovered that jumping to large-scale automated evals too early caused calibration chaos. Their counterintuitive lesson: start with unstructured, intuition-based 'vibing' to quickly identify failure patterns. This manual approach lets teams iterate radically on prompts and architecture without being held back by brittle eval scaffolding.
Once failure modes are well-understood, the team then builds comprehensive evals with clear rubrics, human raters, and LLM judges. They stress the importance of raters explaining their judgments—pass/fail decisions alone miss why agents fail. A striking example showed an agent removing a legally required disclaimer despite explicit instructions, a flaw invisible to aggregate metrics.
Agent traces proved essential for spotting reasoning gaps that pass/fail rates overlook. Traditional ML principles still apply: maintain test sets, monitor disagreement between human and LLM raters, and focus on patterns rather than hyperfixating on single stochastic failures.
For engineering leaders, this means investing in eval infrastructure as a first-class delivery concern. Define launch criteria early, train cross-functional teams on rubrics, and treat eval development as an iterative process alongside the agent itself. The real bottleneck is often evaluation discipline, not model capability.
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
Why a Positive A/B Test Is Not Enough for AI Features
Bumble's PM reveals why a positive A/B test for an AI feature is only the start: low adoption, bad long-tail outputs, hidden costs, and regulatory walls.
Why Your AI Agents Need a Manager, Not Just Permissions
AI agents need HR-style governance: identity, sponsor, and machine-speed oversight. The talk from Gravitee offers a framework but no proof.
Model Choice Barely Matters: Fix Engineering Culture, Not AI Tools
AI model choice explains under 1% of developer output variance, per Jellyfish's 50,000-engineer dataset. The levers leaders control matter more.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.