Загрузка видео...

Не удалось загрузить видео

На главную

The best programmers don't write code anymore. They write a spec. A test. An eval. T Then they turn the AI on and walk away for hours. It runs. It ships. They review. Evals are the unlock most devs are sleeping on. Here's how top agent teams build them right.

691,571 просмотров • 5 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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 просмотров • 5 месяцев назад

A TURING AWARD WINNER STOOD UP AND TOLD A ROOM OF ENGINEERS THAT ALMOST NONE OF THEM DO THE ONE THING THAT ACTUALLY SEPARATES REAL ENGINEERING FROM TYPING, THEY WRITE CODE BUT THEY NEVER WRITE THE BLUEPRINT 56 minutes from Leslie Lamport -- Turing Award winner, creator of the tech behind almost every distributed system on earth. -> His claim: architects draw plans before a brick is laid. Programmers just start coding and hope. That gap is where complex systems quietly break. 04:10 -- A blueprint for software is called a spec. Write what the system must DO before touching how it does it. 10:13 -- Thinking above the code is the skill. The language is just the last, easiest step. 43:23 -- What programmers should really know isn't syntax. It's thinking clearly enough that "done" actually means done. 48:15 -- Thinking is hard, so we skip it. We jump straight to code because typing feels like progress. And this is exactly the wall the new "Loop engineering" hype is about to hit -- people now design loops of agents that write and check code while they walk away. But an unattended loop with no spec just ships broken work faster. Lamport is the missing half: the discipline that makes it safe to leave a loop running at all. You thought the leverage moved into better prompts and better loops. This is the man showing it moved above the code, where almost no one is willing to think. Save this. Read it before you trust a single agent loop ↓

slash1s

15,371 просмотров • 1 месяц назад