正在加载视频...

视频加载失败

"Everyone says AI evaluations are important, so let's actually build one live from scratch.” Here's my new episode with (Arize) where we build AI evals for a customer support agent live, including: ✅ Creating the eval criteria ✅ Labeling the golden dataset ✅ Aligning LLM judges with human scores...

37,177 次观看 • 11 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

McKinsey surveyed 2,000 companies in 2025. 51% said AI backfired on them. Top reason? Inaccuracy. From what I can tell, most of these systems weren't broken. They were unreliable. And unreliable is wayyyy worse because you can't predict when it fails. So I got Ash Tilawat (the Mr. Miyagi of teaching AI) from Gauntlet AI to walk me through the solution. Here's his 2026 framework for evaluating if your AI is trustworthy, reliable, and production-ready: 1. build your golden set Identify 30–50 core requests your AI must handle correctly. The stuff that, if broken, makes the whole system useless. And sit with the person whose job this AI is doing/automating/replacing/helping with. 2. test the weird stuff Your golden set covers common requests. But in production, users don't only ask common requests. So build a matrix of categories (topic x complexity) and fill the gaps. Every gap is a corner where failures can hide behind. 3. build a replay harness Record the exact state of every interaction so you can test prompt changes without burning API calls. Think of it like game film... you don't put players back on the field just to review the play. 4. create your rubric Use an LLM to grade outputs on accuracy, completeness, and tone. But calibrate it first -> run 50–100 examples through human and LLM scoring, find disagreements, fix the rubric, repeat until they match. 5. run experiments New model? Prompt rewrite? Run your eval suite against both versions. Ship if the golden set passes, no regressions, and the cost is acceptable. The teams still running production AI on vibes will be f***** in 2026. But the teams building eval libraries are compounding an advantage that gets harder to catch every month. Competitors can copy your product. They can't copy your test cases. h/t Austen Allred for helping put this together. Full playbook + vid below 👇

Alex Lieberman

71,920 次观看 • 6 个月前

New short course: Evaluating AI Agents! Evals are important for driving AI system improvements, and in this course you'll learn to systematically assess and improve an AI agent’s performance. This is built in partnership with Arize AI and taught by John Gilhuly, Head of Developer Relations, and , Director of Product. I've often found evals to be a critical tool in the agent development process - they can be the difference between picking the right thing to work on vs. wasting weeks of effort. Whether you’re building a shopping assistant, coding agent, or research assistant, having a structured evaluation process helps you refine its performance systematically, rather than relying on random trial and error. This course shows you how to structure your evals to assess the performance of each component of an agent and its end-to-end performance. For each component, you select the appropriate evaluators, test examples, and performance metrics. This helps you identify areas for improvement both during development and in production. (If you're familiar with error analysis in supervised learning, think of this as adapting those ideas to agentic workflows.) In this course, you'll build an AI agent, and add observability to visualize and debug its steps. You’ll learn about code-based evals, in which you write code explicitly to test a certain step, as well as LLM-as-a-Judge evals, in which you prompt an LLM to efficiently come up with ways to evaluate more open-ended outputs. In detail, you’ll: - Understand key differences between evaluating LLM-based systems and traditional software testing. - Add observability to an agent by collecting traces of the steps taken by the agent and visualizing them - Choose the appropriate evaluator - code-based, LLM-as-a-Judge, human-annotation based - for each component. - Compute a convergence score to evaluate if your agent can respond to a query in an efficient number of steps. - Run structured experiments to improve the agent’s performance by exploring changes to the prompt, LLM model, or the agent’s logic. - Understand how to deploy these evaluation techniques to monitor the agent’s performance in production. By the end of this course, you’ll know how to trace AI agents, systematically evaluate them, and improve their performance. Please sign up here:

Andrew Ng

126,478 次观看 • 1 年前

I don't think most PMs realize the PRD is becoming obsolete. For the last decade, the PM's core artifact was a qualitative spec. Clear requirements, user stories, acceptance criteria. The engineering team interpreted it, built something close, and the PM spent two weeks reconciling what shipped with what they wrote. The best AI companies replaced that entire loop with evals. A set of inputs your product needs to handle. A task that generates outputs. A scoring function that produces a number between 0 and 1. No ambiguity. No interpretation gap. Ankur Goyal built the eval platform behind Vercel, Replit, Ramp, Notion, and Airtable. An $800M company. He walked through building an eval from zero on this episode and the score went from 0 to 0.75 in under 20 minutes. That's a PM shipping a measurable quality bar before a single line of product code exists. Here's the part that changes the PM role permanently. When the product passes the eval and users still hate it, the eval is wrong. That's on the PM. Evals make PM judgment quantifiable in a way PRDs never did. You can't hide behind "the spec was ambiguous." There's a number now. Six months ago, PM interviews asked "how do you use AI in your workflow." The next wave of interviews is going to ask you to write an eval. The PMs who can encode user intent as a scoring function are building the one skill that survives every model change, every framework swap, every agent rewrite. Write the eval.

Aakash Gupta

78,275 次观看 • 4 个月前