Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Latent SpaceLatent Space

Why I couldn't build Jev at OpenAI — Diogo Almeida, TypeSafe Co-founder & CEO

From helping build instruction-following models at OpenAI to spending years trying to answer why AI can solve extraordinarily hard problems yet still automate so little real work, Diogo Almeida is betting that the next wave of AI won’t look like chat. In this episode, the TypeSafe founder and CEO joins swyx days after Jev’s breakout launch to explain System One Models: machine-native AI designed for code, calibrated decisions, reliability, and intelligence per dollar. We go deep on Jev and RLCD, the failure modes of RLHF, why TypeSafe refuses to optimize around public benchmarks, and why Diogo believes data and the right task matter more than simply scaling compute. Diogo also explains why he left OpenAI, why refusals and safety alignment become fundamentally different problems when AI is infrastructure, how Jev changes the architecture of coding agents, why AI should eventually disappear into the background of software, and why even with a billion dollars, he wouldn’t pre-train a model from scratch. We discuss: • Why AI can solve extraordinarily hard problems but still fail to automate basic work • What System One Models are and why Jev is built for software rather than chat • RLHF, mode collapse, calibration, and the hidden costs of optimizing for human preferences • Why refusals become a problem when AI is buried inside software dependencies • Why TypeSafe rejects public benchmarks and optimizes for intelligence per dollar • The “bitterest lesson”: why the right task and the right data can matter more than compute • Why TypeSafe thinks of itself as a data lab rather than a model lab • RLCD vs. RLHF and RLVR as fundamentally different North Stars for AI • Why reliability and robustness matter more than simple determinism • Jev’s programming primitives and how intelligence maps into software control flow • Why developers should decompose AI workflows into many small, measurable decisions • How structured state replaces giant prompts and system messages • Why Diogo thinks AI should eventually disappear into the background of software • The “inverse SaaS-pocalypse” and how AI could supercharge existing software • System One vs. System Two intelligence and the limits of reasoning models • Dark data, computer use, real-time intelligence, and Jev’s biggest early use cases • Why Jev could reshape coding agents built around a single-model architecture • Why Diogo says he wouldn’t pre-train even if you gave him a billion dollars • The OpenAI journey that led to TypeSafe and why he thinks most neo-labs are approaching AI incorrectly • Coding agents beyond the KV cache, shared state, sub-agents, and the future of multi-agent software — Diogo Almeida • LinkedIn: https://www.linkedin.com/in/diogomda/ • X: https://x.com/CompleteSkeptic Timestamps 00:00:00 Intro 00:01:29 Jev Launch Week and the AI Economic Revolution 00:04:19 What Is Jev? System One Models and Programmable AI 00:07:23 RLHF, Mode Collapse, Calibration, and Yann LeCun 00:11:58 Programmatic AI, Refusals, and Safety Alignment 00:18:50 Why TypeSafe Rejects Public Benchmarks 00:22:12 The Bitterest Lesson: Data, Compute, and the Right Task 00:26:28 RLCD vs. RLHF and RLVR 00:30:11 Why Powerful AI Still Hasn’t Automated the Economy 00:41:24 Reliability, Robustness, and Determinism 00:49:40 Model Versioning, LTS, Speed, and Intelligence per Dollar 00:55:33 Inside Jev’s API and Programming Primitives 00:59:57 How to Build with Jev: Structure, Decomposition, and Small Decisions 01:19:57 The Inverse SaaS-pocalypse and AI Disappearing into Software 01:34:50 Computer Use, Dark Data, and Jev’s Biggest Use Cases 01:40:17 How Jev Could Reshape Coding Agents 01:42:29 AI Safety, Frontier Pacing, and the Limits of RLVR 01:49:32 Why Diogo Wouldn’t Pre-Train with $1 Billion 01:56:48 The OpenAI Story Behind TypeSafe 02:03:10 Why Diogo Thinks Most Neo-Labs Are Getting AI Wrong 02:09:29 Coding Agents Beyond the KV Cache and the Multi-Agent Future

Diogo Almeidaguest
Sep 21, 20262h 22mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

EVERY SPOKEN WORD

  1. 0:00 – 1:29

    Intro

    1. DA

      Like, how can AI be so unbelievably smart? How can we, like, solve Millennium Prize problems in math but still not automate even the most basics of works? Like, like really basic rote stuff, but we have this, like, supercharged engine of automation that just does not have, like, the right plugs and stuff to plug into all of this economically valuable work. And, you know, like, if the whole company of TypeSafe disappears, like, maybe it'll take, like, a year or two for people to, like, truly catch up. I actually don't know how long it'll take. If, uh-- If model quality matters, then we are gonna be in a very good position for a long time. But, um, it-it, like, it-it, it's done, right? Like, there-- Like, this has changed the path of, like, technological history.

    2. SP

      Before we get into today's episode, I just have a small message for listeners. Thank you. We would not be able to bring you the AI engineering, science, and entertainment content that you so clearly want if you didn't choose to also click in and tune into our content. We've been approached by sponsors on an almost daily basis, but fortunately, enough of you actually subscribe to us to keep all this sustainable without ads, and we wanna keep it that way. But I just have one favor to ask all of you. The single most powerful, completely free thing you can do is to click that subscribe button. It's the only thing I'll ever ask of you, and it means absolutely everything to me and my team that works so hard to bring The In Space to you each and every week. If you do it, I promise you, we'll never stop working to make this show even better. Now let's get into it.

  2. 1:29 – 4:19

    Jev Launch Week and the AI Economic Revolution

    1. SP

      [upbeat music] Okay, we're in the studio. Uh, special occasion because this week, uh, Diogo, my, my good buddy, uh, launched Jev, and, uh, it's been taking over the complete timeline. Uh, how do you feel? What, what's it like to be you right now?

    2. DA

      Emotionally?

    3. SP

      Yeah.

    4. DA

      Um, never been worse.

    5. SP

      [laughs]

    6. DA

      Um, [laughs] like, uh, I'm a ragged corpse of a person right now because there's so much going on, and I'm, like, a technical CEO, so I have, like, a lot of fires to fight.

    7. SP

      Yeah.

    8. DA

      But, like, mentally, it's-- Like, I feel-- I, I say this all the time, and I've been saying this kind of for years in my over/under events. Like, I feel like the entire AI field is like one of those, like, carnival house of mirrors, and everyone is just insane and saying the weirdest stuff that doesn't make sense. And it feels like for just this week, like I'm, I'm on a better in sync with reality and like, oh, people see it now. AI can be so much more than what was once thought.

    9. SP

      Mm.

    10. DA

      And like, yes, we are going to make-- like, like, an AI-based economic revolution is back on the table, and, um, this is fucking awesome. You know? This is fucking awesome.

    11. SP

      [laughs]

    12. DA

      I'm so jazzed the developers get it. It's, it's, uh... Yeah, and I want to show my internal gratitude to the developers and-

    13. SP

      Yeah

    14. DA

      ... I'm so jammed about the community and everything. It's so great.

    15. SP

      Yeah, you were saying yesterday that you decided to prioritize the town, town hall and not a bunch of, like, you know, VIP inv- investor-type people because you wanted to make sure that they are the people that you get, get your most, uh, a-attention, right? The engineers, the developers.

    16. DA

      Yeah, it felt a little like, "Oh man, I'm talking to, like, really important people right now."

    17. SP

      Yeah.

    18. DA

      I probably shouldn't reveal who.

    19. SP

      Yeah.

    20. DA

      But it feels a little bit dirty for me to, uh-- I, I'm, like, perhaps overly genuine in things. Like, it, it feels, like, dirty if, like, in my gigantic calendar event of things to, people to talk to, you know, the community isn't one of those.

    21. SP

      Yeah.

    22. DA

      You know? And actually, in my ideal world, it would be, like, community all the time. I was thinking, "Should I host a town hall while walking to your studio?" And I'm like, "Nah, that's too crazy."

    23. SP

      Sure. Yeah. [laughs] Well, you, you guys have been hosting town halls on the Discord. Discord is now a hundred thousand people. Um, your, your Twitter is-

    24. DA

      I don't follow these stats.

    25. SP

      Yeah.

    26. DA

      So holy shit.

    27. SP

      Your Twitter is blown up. Uh, you know, uh, it was, it was really funny 'cause, like, at AIE, you were like, "Uh, follow me, please," and then you didn't, like, provide even your, your handle. So [laughs]

    28. DA

      I'm a noob. I'm a noob.

    29. SP

      You're such a noob.

    30. DA

      I'm a noob.

  3. 4:19 – 7:23

    What Is Jev? System One Models and Programmable AI

    1. SP

      on everything.

    2. DA

      Thank you.

    3. SP

      We'll talk about more, uh, details a-as you have them, but let's, for people who are, like, living under a rock or just-

    4. DA

      [sneezes]

    5. SP

      Just want, like, the definitive thing, what is Jev?

    6. DA

      [sighs] Let me think about-- That's a hard one.

    7. SP

      [laughs]

    8. DA

      Um-

    9. SP

      Okay, and, and I'm happy to, like, uh, re-ask if you wanna correct-

    10. DA

      No, no, no. I'm happy to-

    11. SP

      Okay

    12. DA

      ... I'm happy to, like, just jam on it.

    13. SP

      Yeah.

    14. DA

      I will say, like, the first thing that I'm relieved about with this question is now I don't have to answer that question to my parents anymore, 'cause ChatGPT can just explain it.

    15. SP

      [laughs] Nice.

    16. DA

      Um, so, uh, the way I see it is we ne-need a new class of models. Um, we're not attached to naming that class of models. Um, our the most accurate name we've come up with is System One Models.

    17. SP

      Yeah.

    18. DA

      There will be reasons, but it's-- There's a reason why we don't call them decision models because, like, they will be-- Like, System One is beyond that. Uh, that's all I can say. Um, we didn't expect this to be our big launch, so we have stuff in the tank. Um-

    19. SP

      You should've said low-key research preview. [laughs]

    20. DA

      Um, it kinda was, right? It kinda was. But, um, we-- So there's a class of models that we describe them as, like, machine native, System One, large programmable.

    21. SP

      Mm-hmm.

    22. DA

      I think these are is the class of models, where the goal is for code to be the consumer. So, um, as opposed to, um, lar- um, pre-trained large language models, which are meant for, like, auto-complete of the internet or RLHF models like chatbot instruction-following models, which are meant to, like, reply to text, um, or RLVR. It's in a weird gray area with R-RLHF. Like, these are meant to have things that directly are consumed by code, hence the name TypeSafe. So the thing we really, really, really want is to have, like, AI Like, be as powerful as possible, and we think the way to do that is to integrate it with software. And we are designing everything, you know, beyond just the outside, the deep internals of the model to be optimized for software. So, uh, number one, Jev is our first large programmable model, um, or a system-one model, whatever you want to call it. Um, Jev is meant to be optimized for intelligence per dollar, uh, hence the name Jev. You know, uh, I mean-

    23. SP

      Jevons Paradox

    24. DA

      ... Jevons- Jevons Paradox, yeah. Um, and it's optimized for intelligence per dollar. I love this debate with people about what is the most important between reliability, cost, calibration, and speed. Um, and Jev is meant to be... Jev will be the name of models that will be on the frontier of intelligence per dollar. There's other ways to optimize it, like, uh, ML, or at least if you're good at ML, it's all about trade-offs. And, you know, we are just going all out on that.

    25. SP

      Yeah. And, and to me, like, calibration is one of the new things that people weren't talking about as much. We've done an episode-

    26. DA

      Mm-hmm

    27. SP

      ... uh, in the past, uh, with Clémentine Foreyo of Hugging Face, uh, where they were like, yeah, a-actually, um, y- they are just are... You know, and this is your, your argument about RLHF, is they're mode collapsing towards what you want to hear the most-

    28. DA

      Ooh

    29. SP

      ... or what is most likely, uh, instead of, like, their own internal confidence about

  4. 7:23 – 11:58

    RLHF, Mode Collapse, Calibration, and Yann LeCun

    1. SP

      a, a, a thing.

    2. DA

      Can I soapbox on that for a second?

    3. SP

      Go ahead.

    4. DA

      Or-

    5. SP

      Yeah, yeah

    6. DA

      ... cool. Uh, like, um, uh, I've been heard that your audience is the most technical, so I actually want to get into that.

    7. SP

      [laughs] Yeah.

    8. DA

      Um, and if-- I went through extreme precision to make sure everything in our launch video is accurate and real. Apparently, that's very unusual. One of the things that no one paid attention to was the downsides of RLHF, in particular, mode dropping. Um-

    9. SP

      Mode dropping or mode collapse?

    10. DA

      Uh, it's the same thing.

    11. SP

      Is that what-- How you gonna-

    12. DA

      It's the same thing.

    13. SP

      All right.

    14. DA

      And, um, I, I, I wanna have a blog on this eventually, but I, like, want to tell as many people this as possible 'cause I think it's a very interesting thing. So the spicy take, I believe in Yann LeCun a lot. Uh, I think Yann LeCun's takes are actually among the closest to-

    15. SP

      What, what about this? [laughs]

    16. DA

      Well, do you want to address this now or should I go on mode collapse?

    17. SP

      No, no, no, later.

    18. DA

      Okay, okay.

    19. SP

      Go, go, go mode collapse. I don't know.

    20. DA

      So I actually think that among takes, Yann LeCun's is among the most accurate. Um, but he has this very famous/infamous slide about, uh-

    21. SP

      The cake

    22. DA

      ... L- LLMs are doomed.

    23. SP

      Okay.

    24. DA

      You know, like that one where he's, uh, where he, like, has, like, a pie chart with, like, this tiny par-- tiny little thing-

    25. SP

      Oh, that

    26. DA

      ... and says that as you increase sequence length, um, the probability of it making an error goes to... Yes, this one, this one. I love this one, um, because it's one of these things that seems mathematically obvious but is obviously wrong, right? Like, it's mathematically obvious, but it doesn't empirically hold, and this is my favorite thing to teach people about. Like, where you, you-

    27. SP

      What's the disconnect, right?

    28. DA

      Exactly. And, um, may I or you want to tell me, uh-

    29. SP

      About mode collapse?

    30. DA

      Oh, no, no. Uh, so mode coll-collapse is related to this.

  5. 11:58 – 18:50

    Programmatic AI, Refusals, and Safety Alignment

    1. DA

      I just think there's, like, so many diamonds in the rough lit all over the research world right now that haven't been polished because people don't know how to, like, do the right task, and I think that what our launch did, it, does it kickstart us as a company? Like, yes. Will it be great for us as a company? Yes. I think it's gonna be, like, even greater for this direction of, like, programmatic AI. You know, there, there was going to be, like, a gold rush On top of us for- 'cause like software is super fucking charged. But I think there's gonna be a gold rush parallel to us as well on like all the different ways we can expose things to make software more powerful so people can make even cooler stuff, and then we are back to like early internet energy. You know?

    2. SP

      Yeah.

    3. DA

      And, and I think that's why like, you know, the Twitter is just like, "Jev, Jev, Jev." You know? Um, it's, it's like, it is like a party.

    4. SP

      It's inspiring because it's, it's like so different than what we're used to, which is, "I'm sorry you can't do this, but we do scaling laws and only the big labs can do it." Right?

    5. DA

      That, that-

    6. SP

      [laughs]

    7. DA

      ... uh, actually, c- if I... I'll, I'll nick tangent if that's okay.

    8. SP

      Yeah, yeah.

    9. DA

      I, I think you might enjoy this. Might-

    10. SP

      Really? Five, five tangents in. No, it's, it's going to be so it's fine. Yeah.

    11. DA

      Oh, it's... Yeah, I get lost in all my tangents.

    12. SP

      It, this is gonna be horrible for the listeners to figure it out, but they, they're gonna figure it out. It's fine.

    13. DA

      Yeah, we can edit it out.

    14. SP

      This morning. Yeah.

    15. DA

      Um, [laughs] so popular thing on Discord, um, that people keep asking me, I haven't had the time to explain it yet, is why am I opposed to safety alignment and why do we not refuse? Um, I'm not opposed to safety as a principle, but I think that safety alignment is generally misaligned with users. Um, and, uh, refusal is just like obviously a type error. Like if you're a human being and you're chatting with like a, you know, a model or whatever, you're cloud coding, and a refusal happens like, "I'm sorry, I can't read DNA.py," um, that's an annoying time. It's anno- it's, it's annoying, right?

    16. SP

      Mm-hmm.

    17. DA

      But you can work with it, right? And you're forced to work with it 'cause of Stockholm Syndrome. Um-

    18. SP

      [laughs]

    19. DA

      ... uh, t- I have stories about that t- too. I, I need another tangent deep in here. But like if you ever want this in a dependency running in the background, what happens if that refuses? What if someone else is using that dependency? They don't know what that system is. Like, like you want the software to just stochastically break because a user sent like a weird message in there?

    20. SP

      Mm.

    21. DA

      Like that is, um, like straight up insanity. It, it, it's coming from a place of like people who do not understand software, do not understand programming.

    22. SP

      Mm.

    23. DA

      And like they are obsessed with like, I believe this, um, horseless carriage of like AI coworker instead of unearthing like the full power of AI.

    24. SP

      Fair enough.

    25. DA

      Yeah.

    26. SP

      Uh, you, you want something that is the core kernel that is, is usable everywhere.

    27. DA

      Yes. Exactly. Like the cognitive core, right?

    28. SP

      Yeah.

    29. DA

      And you need this thing to be s- like so general, so optimized for its use cases. You want it to be like, you know, you want it to work on all the future use cases, all the weird shit that people are doing.

    30. SP

      Yeah.

  6. 18:50 – 22:12

    Why TypeSafe Rejects Public Benchmarks

    1. DA

      Hell yeah.

    2. SP

      I think it's probably takes two sentences from you about, like, you will not, uh, y-you're not being that restrictive about your API. Like, clearly-

    3. DA

      Oh, yeah. Obviously, yeah

    4. SP

      ... ideologically, you would take y- your role as a platform very seriously.

    5. DA

      Yes. Uh, yes. Uh, uh, I don't know what you're referring to, but, like, this was-- Uh, I, I've seen a couple of things about, like, benchmarking.

    6. SP

      Yes.

    7. DA

      Like, obviously, we're not stopping people from do-- Oh, man, I should be careful about what I say, I'm realizing. [laughs]

    8. SP

      [laughs] No, you said it, you said it publicly that-

    9. DA

      Yeah

    10. SP

      ... that was in the preview period. You didn't take it out for the launch.

    11. DA

      Yeah. Okay.

    12. SP

      And now you're gonna take it out.

    13. DA

      So the team is doing stuff that-

    14. SP

      Yes

    15. DA

      ... I'm not even aware of, so it's great to know the team communicated that.

    16. SP

      Mm-hmm.

    17. DA

      I asked them to check in with the lawyers about that.

    18. SP

      Yeah.

    19. DA

      Like, we are obviously not stopping people from doing that type of thing. I am extremely in favor-- So I'm extremely anti-public benchmarks. Um, I'm extremely in fav-- I'm medium about private benchmarks that are proxies. Um, you know-

    20. SP

      So a-are you worried about, uh, sat-saturation or, like, uh, training on public benchmarks, so it's, like, e-easy to cheat?

    21. DA

      Um, not only is it easy to cheat, there's a lot of ins... So, uh, I think that we are-- Or, or anyone who's, like, competition with us that, you know, vaguely there is-- Like, you could say, like, the-

    22. SP

      There's, like, 50 Jev clones. Yeah.

    23. DA

      Well, uh, sure, sure.

    24. SP

      Yeah.

    25. DA

      Uh, w-these-- Let's say that there's various competition.

    26. SP

      And we'll talk about those. Yeah.

    27. DA

      Or let's just say that there's l- there-- Let's just assume that there's an industry two years from now of people who are doing similar things to us. The thing that we are selling is intelligence per something, per, like, dollar or per second. Um, the-- No o- Like, people obsess about the cost and the speed. Um, I believe that that is-- It's cool, but, like, the thing that matters is the intelligence. Like, the cost and the speed are, like, th- are bad things. You know, you're paying them for something, and you need the thing back, and the intelligence is what truly matters. The problem with intelligence is that there's a je ne sais quoi to it, right? Like, the, like, uh-

    28. SP

      Mm

    29. DA

      ... the, the good model smell. Like, the thing that happened after we launched of, like, two hours later that actually went way bigger than the video, which was like, "Holy shit"-

    30. SP

      This is actually usable

  7. 22:12 – 26:28

    The Bitterest Lesson: Data, Compute, and the Right Task

    1. DA

      Hell yeah. Um, t- like, you know, Suchin says that algorithms beats compute very roughly. Um, data matters way more than compute, obviously. And doing the right task, having the North Star is, is, is the hardest, most important thing. This has happened, um, in LLM land twice so far, right? Maybe 2.2 times. You know, there's RLHF, which, like, shifted the task to instruction following. No one realized that that was possible. Um, RLVR did, like, a tiny little, like, edit to the, to the direction, and now us, right? RLCD. We have a new task, and the goal is, you know, programs in the loop. And, um, yeah, data matters so, so, so-

    2. SP

      Right

    3. DA

      ... unbelievably much.

    4. SP

      So, so-

    5. DA

      It's like I can't, I can't emphasize it less.

    6. SP

      Yeah. You consider yourself a data lab rather than, like, a model lab. Is that-

    7. DA

      Absolutely

    8. SP

      ... something-- That's the wording you guys use?

    9. DA

      Yeah, yeah, yeah. Uh, we are-- We will always, like, care so much about data. Um, to me, model capabilities means data. Data is so unbelievably complicated, and that is what gets nines. Like, you have no idea how, how much data can shift everything. Data is so important.

    10. SP

      Yeah.

    11. DA

      Holy crap.

    12. SP

      Um-

    13. DA

      So if people are looking for a job, um, we are hiring infinite data people. Actually infinite.

    14. SP

      [laughs] What is a good data person? Like, um, you know, clearly somebody who cares about reading through the, the transcripts of, uh, whatever. You said, for example, that y- all your data is synthetic.

    15. DA

      Yep.

    16. SP

      But, uh, that's only, like, the scratching the surface, right?

    17. DA

      Yeah.

    18. SP

      Like, it's not... Like, synthetic, so what, right? Synthetic, but we have a people with a lot of taste and a lot of care looking at, looking at these, articulating what's wrong, going back, regenerating. Is, is that what a good data person is these days?

    19. DA

      [sighs] Let me try to figure, figure out how to... Like, it's, it's super complicated, and, like, I literally onboard the data people with a Talk that I assume is longer than this podcast will end up being. So I will try to say, like, the high level of it. So number one, we don't do the kind of synthetic data that people ki- well, I'll do a-- actually, number zero. Um, data and synthetic data depends on your task. Like the shape of your data, uh, s- the shape of your task changes the data. Like RLVR's data is kind of environments, right?

    20. SP

      Yes.

    21. DA

      Um, RLHF's is the human feedback, you know? Um, each task has its own unique kind of data, and we, of course, have our own unique kind of data, right? Um, so number one, we have that. Uh, number two, um, the thing I, the reason why we don't want to train on our users' data even if we could, right? Like, we could probably ask for any terms right now, and it'll, w- w- we-- I don't know if it would make a difference. We truly don't want that, um, because no matter what, the real world data has so much bias. There's like a power law of, like, people, like, asking the same things where you'll end up, like, overfitting to it and, like, fracturing to it and all of that. And number two, we are, like, aiming for, like, a complete sci-fi future years from now where, like, these models are going to be, like, the general infrastructure, layers and layers and layers and deep down the stack to, to, like, things people can't even imagine. Like, I would like to think of our model, like, kind of like, like, you know, UDP as LLMs and TCP as our models. All sorts of stuff can be built on top of that, and we need to be able to nail those futuristic use cases such that software developers can actually build that futuristic stuff. And the way to do that is even if we had all of the data of the present, um, we would just overfit to the present, and then it wouldn't work. What we need is to, like, it, it, it almost feels like a, like, uh, they're, like artists. You know? They study this cognitive core. Our cognitive core is, like, way less jagged than anyone else's, and then they find the jaggednesses, and then they address them surgically in a way that, a-and you can never perfectly do this, right? But they do it in such a way that it addresses it in every single possible, like, dimension, past, present, future.

    22. SP

      The general case rather than the specific case.

    23. DA

      Exactly. And, like, that requires a lot of intelligence every time.

    24. SP

      Um, okay, so we mentioned a little bit, you, you, you sort of criticized my thinking as our, like, very RLVR influence, which is, like, very fair. Um, let, let's, let's actually mention RLCD.

  8. 26:28 – 30:11

    RLCD vs. RLHF and RLVR

    1. DA

      Ooh.

    2. SP

      Um, which obviously you have some secret sauces. To my knowledge, you've never actually published a paper or anything like that on it. No, right?

    3. DA

      No, not yet.

    4. SP

      Um, but, like, what, what should people get from this? Like, what, uh, can you give people some confidence that you're just not just making up jargon for the sake of sounding cool, right? Like, uh, one thing for me is, like, calibration I do think is, uh, to me, like, well understood because we've covered it in, on the podcast.

    5. DA

      Yeah.

    6. SP

      But I, I don't know what you mean when you say RLCD versus what people are familiar with.

    7. DA

      Great. It's a great question.

    8. SP

      Yes.

    9. DA

      And actually, I will give a related question.

    10. SP

      Okay.

    11. DA

      Um, what is RLHF?

    12. SP

      Okay.

    13. DA

      Right? And actually, RLHF means multiple different things, right?

    14. SP

      Okay.

    15. DA

      Like, there's the RLHF of the original, I think it was, like, Paul Christiano teaching a robot to backflip or something like that. Uh, wasn't there something like that?

    16. SP

      Was that it?

    17. DA

      That, that was the original R-

    18. SP

      I, I referenced the PPO paper, but I don't, I don't know.

    19. DA

      Um, and, uh, so, uh, PPO is not necessarily from human feedback, if I recall.

    20. SP

      Okay.

    21. DA

      Um-

    22. SP

      That's true

    23. DA

      ... but I, but I believe it was, like, an OpenAI alignment work that could teach hard-to-specify outputs like a backflip. I'm not a hundred percent sure. Um, and then there was actually learning to summarize. You know, this was work, um, by a bunch of the, the team that helped with, um, instruct-- a-and co-authored, um, the instruction following paper, which was teaching doing PPO on language models.

    24. SP

      This is, this is the, uh, uh, sorry. Uh, I'm trying to, trying to [laughs]

    25. DA

      Yeah.

    26. SP

      Trying to manipulate this, this thing. Uh, this is twenty seventeen.

    27. DA

      Yeah.

    28. SP

      All right.

    29. DA

      Um, I-I'm not a hundred percent sure, but, like, that looks quite right.

    30. SP

      Yeah.

  9. 30:11 – 41:24

    Why Powerful AI Still Hasn’t Automated the Economy

    1. DA

      But to me, like the pre-Jev world was a tragedy because it, it, it sounds arrogant. Uh, uh, hear me out.

    2. SP

      No, no, no. I strongly believe you. [laughs]

    3. DA

      Cool. Uh, it sounds arrogant, but like I felt this way since long before I even had-

    4. SP

      Yeah

    5. DA

      ... a company.

    6. SP

      And I can, I can vouch that, uh-

    7. DA

      Yes, I've been talking about this for so long

    8. SP

      ... you, you said this at Arounder for like three years.

    9. DA

      Yeah, I've been talking about this for so long. And, and I've been saying it because I thought it would've been easier. Um, they say they do not do things because they, it, they're-

    10. SP

      It is

    11. DA

      ... easy. They, 'cause they thought it was easy. So-

    12. SP

      Yeah, exactly. Exactly

    13. DA

      ... something like that.

    14. SP

      Exactly. Exactly.

    15. DA

      I, I thought it, this whole project would take a week. Um-

    16. SP

      [laughs]

    17. DA

      ... and I was unbelievably wrong. So I am so sorry to everyone at OpenAI [laughs] that I thought... I was like, "Man, I'm solving this right now." Um, but, uh, like I think that the tragic thing is when... Well, I think overpromise, under-delivery is tragic too, and like AI is super extreme on that axis, and I think RLVR is like the main... Well, both RLVR and RLHF are extreme perpetrators of this. Um, but like it, to me, it's like, it's just, there's just so much potential there. Like AI is clearly so smart. I, smart. I love this in my talks, you know, when I ask people like, "How can AI be so unbelievably smart? How can we like solve Millennium Prize problems in math, uh, but still not automate even the most basics of works?" Like, like really basic rote stuff that like the, you know, it, it, it doesn't take like extremely smart people to do this. It's not a satisfying job. Like there's other things these people could be doing, but yet we need them to do like this ba- like super basic, non- unsatisfying stuff because, you know, like we can't automate it yet. But we have this like supercharged engine of automation that just does not have like the right plugs and stuff to plug into all of this economically valuable work. And, you know, like if the whole company of TypeSafe disappears, like maybe it'll take like a year or two for people to like truly catch up. I actually don't know how long it'll take. If, uh, if model quality matters, then we are gonna be in a very good position for a long time. But, um, it, it, like it, it, it's done, right? Like there, uh, like this has changed the path of like technological history.

    18. SP

      Yeah.

    19. DA

      And like we will be exploring that space as a field.

    20. SP

      Yeah. I, I think I, I def- definitely agree with that. Um, you've created possibility. So I think, you know, if I can paraphrase so that people can un- also understand, uh, you should not take the success of TypeSafe and Jev as just like, well, you know, that is a new, new model type. Now we're done. We go back to business. Like, no. Like, actually, there sh- there are like five other model types that you should be exploring, and like let a thousand flowers bloom.

    21. DA

      Ab- absolutely.

    22. SP

      Right?

    23. DA

      Like early internet-

    24. SP

      And some of that, some of which you will probably also do.

    25. DA

      Of course, yes.

    26. SP

      Yes.

    27. DA

      Early internet energy.

    28. SP

      [laughs]

    29. DA

      I think it's back to tech utopia. You know, it's no longer like, oh man, like sometimes my coding agents work, but the, all of the best ones are hoarded internally.

    30. SP

      Yeah.

  10. 41:24 – 49:40

    Reliability, Robustness, and Determinism

    1. SP

      of a kind.

    2. DA

      And nines.

    3. SP

      And nines.

    4. DA

      It's, uh, like, like-

    5. SP

      Which uptime is in my-

    6. DA

      Oh, uh, but, but that's part of it. But like there's reliability in, um, like how intelligent the thing is, like how consistently does it do the thing that you want? And I think that like the, the big reasoning models are very smart. In my opinion, they still lack reliability.

    7. SP

      Mm.

    8. DA

      I think there's many use cases where you, they look like they should be smart enough to automate their work. There is economic incentive at, to automate that work, yet still they're not reliable enough as at an intern because they're optimized for different things. Uh, so like I think that there's the reliability of being able to like trust the outputs and also we are... Like, like there are dimensions of reliability that we are not yet at that I'm like so excited by.

    9. SP

      Yeah.

    10. DA

      You know, like I want to automate the easy work before the hard work. You know, like, I think that that's just a common sense thing to do. Um, but to me, we will be sufficient... I don't know if there's a such thing as sufficiently reliable, but I wanna get so good that people don't even need to try the model to know that it'll work. It's like, that's, like, what flow state is in programming, right? Like, I'm just, like, writing queries because I need intelligence in here. And, you know, like, when, for non-trivial branching, I can just write it in in, like a, like, like a TypeSafe SystemOne query and then get the results out and it just branches accurately. Like, that would be so, so good. Like, that's the, that is the dream.

    11. SP

      Yeah.

    12. DA

      And that is, like, uh, going to be, like, a long, long slog.

    13. SP

      Yeah. We're gonna go into your API designing a little bit-

    14. DA

      Ooh

    15. SP

      ... just, just to give people examples and, like, maybe paths not taken, that kind of stuff.

    16. DA

      Mm-hmm.

    17. SP

      Um, one thing up the front that I do wonder about in terms of reliability is I notice that there's no seed. Uh, there's no, uh... And, and so basically, same input, do I always get the same output?

    18. DA

      Hmm. So-

    19. SP

      And if not, why not?

    20. DA

      Oh, great question. So this is actually, like, a common question we have between, um... So reliability is actually a catchall. Like, whenever AI can't automate something, it's due to some form of reliability. Could be, like, type safety. It could be determinism. It just could be, like, it's, uh, it's jagged, right? So, um, reliability is a catchall. Uh, I just think that it's also a catchall for, like, what the North Star is. Um, re- determinism is, like, same inputs, same outputs. I do believe that this is, like, slightly interesting for unit tests, but I believe that to be the wrong North Star. I, I believe robustness is what people... I, I don't wanna tell people what they really want, 'cause that would be a little arrogant of me.

    21. SP

      [laughs]

    22. DA

      I believe that that is, like, the more important property. Um, uh, you want, um, given similar inputs, get similar outputs. And it's kind of wild how unreliable LLMs are.

    23. SP

      Hmm.

    24. DA

      Uh, like, a, a way that we test this is you put, like, UUIDs in, in, like, little-

    25. SP

      Yeah, yeah

    26. DA

      ... I think they're called nonces-

    27. SP

      Mm-hmm

    28. DA

      ... in, in the prompt. And what you want is similar outputs from all of those 'cause it's truly semantically the same question, and that is the part where you really want... Th- like, like, like, that robustness is where, like, people get, like, burnt with AI making decisions. So I think that is the, a super-duper important property. We could also have determinism. That is, that is a thing that can be available. As far as I can, like, mentally model for programmers, like, it, it, it, it could be valuable for some use cases, so, like, please educate me, um, in comments or you. But, um, my s- in, in general, it's easy... Determinism is something you can, like, trade off for better cost. You know? Like, we are, we are constantly wanting to be on the intelligence per dollar frontier. We are doing, like, absolutely disgusting things to be there. You know, like, this is, um... I, I, I shouldn't say this, but no one's here to stop me.

    29. SP

      [laughs]

    30. DA

      Um, you know-

  11. 49:40 – 55:33

    Model Versioning, LTS, Speed, and Intelligence per Dollar

    1. SP

      it.

    2. DA

      We will not change our models when we deploy them. That is insane. We care about developers. Like, like, like it makes sense if you're... So doing something like that, a- again, this is the problem with a for, first-party product and an API. It makes-- You can do whatever you want in a first-party product, right? Like, like more power to them, whatever gets that experience. That is fine. With an API, you obviously can't do that. But I will say that we, uh, plan to move a lot faster than many people are used to model providers, uh, doing things. So we will be launching new models a lot faster than people think, and we are not promising long-term support for the models because we think that there's lots of improvements to have. So, um, there is a world that we might temporarily LTS what is right now Jev 1.13.0. We might do that because so many people are using it, and I know developers hate breaking dependencies. The alternative is fracturing our fleet, and that is a very bad vibe for everyone. It's gonna be hard.

    3. SP

      Yeah, you can't have like 100 different versions of the model. Yeah.

    4. DA

      Exactly, and if we're iterating very fast, there would be a lot of those versions as well.

    5. SP

      Yeah.

    6. DA

      So, um, we, we do want to have not just a LTS-supported thing eventually, long-term support. Um, we want a really sick way of doing that. We have like research stuff cooking in that direction, and I think it's gonna be the most pro-developer thing ever.

    7. SP

      Yeah.

    8. DA

      Um, but it is not yet our current models, and I'm not promising that we will be able to keep the exact same models. They will get smarter every time for sure.

    9. SP

      Yeah.

    10. DA

      And my sense is that even our model iterations, where it already is smart, um, it, between model versions the, the changes tend to be even smaller than the string models calling them twice. But when, when it, we go from like, you know, jagged to like wow, um, that is where the big deltas are.

    11. SP

      Yeah. Uh, one, one thing, one thing that's beautiful about LTS same models is that actually you can also port them to other silicon.

    12. DA

      Mm-hmm.

    13. SP

      Uh, I don't, I don't know if you've thought about this.

    14. DA

      No comment. [both laughing]

    15. SP

      Okay.

    16. DA

      So I care about intelligence per dollar.

    17. SP

      Yes.

    18. DA

      Right? Um-

    19. SP

      But speed.

    20. DA

      What?

    21. SP

      Speed as well.

    22. DA

      We'll see.

    23. SP

      Yeah.

    24. DA

      We'll see. Honestly-

    25. SP

      I mean, it's a whole part of the inference tech tree that is like, I mean, exploding in the past year, right?

    26. DA

      Yeah.

    27. SP

      Like that you can, you can move to like a Cerebras-

    28. DA

      Yep

    29. SP

      ... um, an Etched or whatever and get like the hundred, hundred thousand times speed up.

    30. DA

      Yeah. Like I, uh, I think that intelligence per second is like a different metric, and we've even talked about like things like intelligence per dollar times second and like metrics like this. My guess on like Jevons paradox occurring, or at least the Jev series of models, and the thing I like hunt people down about internally is like I don't care how much smarter it is, it needs to be in the pre-different tier. So like, like that is what the brand of Jev is. It is the best thing at intelligence per dollar. For intelligence per second, we'll see. I, I think that it's an intriguing thing. I know that there's many industries that are like extremely dependent on real-time stuff, and they will like, like intelligence per second means tons of dollars for them. But we'll see. I, I, I, I'm, I, I would love to like do both and like have the market correct me either which way.

  12. 55:33 – 59:57

    Inside Jev’s API and Programming Primitives

    1. SP

      choices-

    2. DA

      Ooh

    3. SP

      ... mostly because this is the only podcast that will ask you these, these kinds of questions.

    4. DA

      Oh, hell yeah. Hell yeah.

    5. SP

      Um, so you have three primitives. Um-

    6. DA

      Yeah

    7. SP

      ... choice, score, null. First of all, null, where is that from?

    8. DA

      Um-

    9. SP

      Is that-- is this, like, a term in the, in the literature or what?

    10. DA

      Uh, now-

    11. SP

      I don't know

    12. DA

      ... now it is.

    13. SP

      Yeah.

    14. DA

      Um, we debated this a lot.

    15. SP

      [laughs]

    16. DA

      We debated this a lot. Um, it is, you know, it is bool-ish, right? Like true/false. Um, it is-

    17. SP

      But it's continuous.

    18. DA

      Yes, exactly. Uh, so, so first, the origin of the name is Bernoulli.

    19. SP

      Ah.

    20. DA

      Yes, so it's-- th-that's why it's even spelled that weird way. That is, like, a subset of the name Bernoulli from, like, a Bernoulli probability-

    21. SP

      Right

    22. DA

      ... which is actually what that is. Um, so that is the origin of it. We were debating this a lot. We liked Pbool, we liked Pool. We, we, w-we were wanting to call it, like, a pool party, but then no one let me. Um, you know, we had, like, a bunch of, like, other arguments about that, and null, we figured, was, like, the best thing. The-- our, our rationale, and, like, this was actually the same thing with Jev too, um, is that we think that we are, like, an irreverent, insane bunch, and programmers don't care. You know, like, if Jev is just gonna be a string, we didn't expect it to catch on or even have puns or anything like that, right? Actually, there was a lot of hate on the name internally. They've all apologized except for one person. Um-

    23. SP

      Still holding strong.

    24. DA

      Yes, uh, our mutual friend. Um-

    25. SP

      Okay, okay.

    26. DA

      Yes, yes, yes, yes. Um-

    27. SP

      I respect her for that.

    28. DA

      Yeah. Uh, yeah. Uh, she wanted Jev to be called Meow.

    29. SP

      She would, of course.

    30. DA

      Yes, of course.

  13. 59:57 – 1:19:57

    How to Build with Jev: Structure, Decomposition, and Small Decisions

    1. SP

      Yeah. Um, any other-- So, uh, any nuance you wanna go through for-- L-literally, this is for the Jev people who are, like, deciding to really invest in Jev. You are the expert, right? Um, I'm just, like, wanting to provide more background for them on, uh, API choices, um, you know, how they should use some of these, these things like legends, confidence, um, how critical in your testing, um, you know, like how, how... Like just any sort of like pro tips that you, like, want to offer people-

    2. DA

      Hell yeah

    3. SP

      ... when we're down at this level.

    4. DA

      Thank you. I love this. Um, no, no, no.

    5. SP

      This is why we're here.

    6. DA

      This is-- Hell yeah. I didn't expect this, and actually, I-- no one has asked me this, um, in probably, like, months when I was, like, onboarding, like, our DevRel.

    7. SP

      Okay.

    8. DA

      Um, so sick. Um- So our model is designed for being like deep in the insides of computer programs in the future. We like unironically believe that this will be much more massive than anything people are even considering today. And our model might not be ready for that, but we are like continuously working for that future. It will never be good enough at these shallow tasks. Um, uh, uh, sorry, it'll never be g- like, like we're not just gonna cle- keep on climbing the shallow tasks. We want to be deep in the guts of programs because that's how you make software powerful. All the s- all the types inside of our, um... This is an actually an output.

    9. SP

      Mm-hmm.

    10. DA

      Um, but all the, um, all the parts, uh, of like the, uh, the, the input, like the state, the instructions, the criteria, all of them can be structured JSON objects.

    11. SP

      Mm-hmm.

    12. DA

      That way, like programs can like insert them in the right spot, and you don't need to like put things-

    13. SP

      Pieces

    14. DA

      ... into templates. Exactly. So if ever... I, I think people don't read into this part enough, and they think it's all strings, and that's, that, that's fine. Um, but these are all meant... Like, like I would say that if you're using like a template, like turning it into like a system message or something, you are thinking in like the old way. You know, we should be making things as easy for computers to understand because that structure is truly there, right? Like, it would be weird in like, like a programming language to have like all of your numbers in, then you pass it into like... You turn it into a string. Normally, you do that for printing when, when you have a human in the loop, right? But for like within the computer, you want to be passing like nested structure that is semantic all around, and we are really gonna be optimizing our model. It, the model's pretty optimized for this, but the thing is every different nested level of structure is harder to reason about, and we want-- we are really cooking hard in that direction. I think people should keep cooking in that direction because it makes the code like so much more legible and beautiful and like agnostic to like the, the implementation details. It's like, here is my state. You know, like here's my function state. Like think of it, think of it as like an AI function. Which subsets of my state, which is like all the variables you have available, should I pass in here? System messages are like disgusting global variables where you just put everything in there, and you put all those-

    15. SP

      Slop, yeah

    16. DA

      ... instructions at once. And then y- you know, like you s- you hope that every single instruction gets nailed instead of asking the questions in parallel.

    17. SP

      Okay.

    18. DA

      And, uh, also, I would recommend, I, and I truly say this not from like a, like it makes me money perspective, um, I truly recommend asking lots and lots of questions. Break them down, make them smaller, and like really decompose. Like no matter if the models can do it today or not, I believe that the biggest like, um, s-saving grace of like what's happening this week will be people's code bases, AI code bases are gonna be so much better. You know, like if you decompose problems into simple decisions, every single one of these things is extremely evaluable. Like, like a AI beforehand is big system message, and then maybe you have like another big AI-

    19. SP

      Big output, yeah

    20. DA

      ... to see like if it actually does this. That's nuts, you know?

    21. SP

      [laughs]

    22. DA

      It's kind of crazy. Like, and it, it, it, it's... That was our Stockholm syndrome, right? But like that's kinda crazy. Like if you wanna say like, "Hey, don't read this sub-directory or don't pass any API keys to DeepSeek or whatever else," like that should be programmatically, basically guaranteed. And you know, you'll never have guarantees of any machine learning model, but like by breaking it down, you can actually s- you can actually measure it, right? Like-

    23. SP

      Yeah. You can verify that it was actually called or-

    24. DA

      Yes, and like our model, our model, like the, the interface itself is so verifiable. This should be like a sigh of relief.

    25. SP

      Mm.

    26. DA

      You know, like it's, it's, uh, it- it's just gonna lead to way better engineering.

    27. SP

      Yeah. I think I get that. Um, and, and so, you know, one of the reasons people didn't use to do this in the past is because they would just call a, a small LLM, right?

    28. DA

      Yep.

    29. SP

      And it's still too slow, it's still too expensive versus chunking everything that... I've done exactly this myself.

    30. DA

      Yep, yep, yep.

  14. 1:19:57 – 1:34:50

    The Inverse SaaS-pocalypse and AI Disappearing into Software

    1. SP

      Mm-hmm.

    2. DA

      It's gonna be fucking awesome. It will not cause mass unemployment, but it will cause, like, a whole bunch of awesome shifts, and wor- the world will be a lot better. And also, like, I'm really tired of AI always being the foreground character, uh, of things. Like, I think that the world should just be more delightful, and AI should just help with that.

    3. SP

      Hmm.

    4. DA

      You know, and I-

    5. SP

      Just, like, disappear into the background.

    6. DA

      Exactly. You know-

    7. SP

      Yeah

    8. DA

      ... like, uh, the, I, I say this in my talks. Like, how can it be that 2019 software, like software, SaaS, whatever, uh, super-duper valuable, right? It's 2026 now. How is the software basically exactly the same despite AI being so freaking awesome, other than sometimes having a chat box on the side, right? Uh, that, that, like, that kind of works but doesn't allow you to make decisions that the companies have stakes in because they, they can't be trusted to make decisions. That to me is nuts. You know, there, there's so much economic incentive for this, and I, I think it's going to be, uh, like a, like an inverse SaaS-pocalypse. I think SaaS is going to be super charged by this. They're the ones who are, like, most in the know of what things are valuable to automate, and it's gonna be, like, a crazy time.

    9. SP

      Yeah. I, I think, I think so too. It's a s- it's a beautiful thing that you've unlocked, you know?

    10. DA

      Yeah.

    11. SP

      Um, you mentioned one thing here, which I don't know if it's, uh, like, directly here, which is what is a system one problem and what is not? What, what is a system two problem? Like, you know, um-

    12. DA

      Fuck.

    13. SP

      [laughs]

    14. DA

      That's a hard one.

    15. SP

      [laughs]

    16. DA

      That's a hard one, my friend. Um-

    17. SP

      'Cause people now are just trying to Jev everything, right?

    18. DA

      [laughs]

    19. SP

      Which, like, probably is gonna fail.

    20. DA

      Love Jev everything.

    21. SP

      Right?

    22. DA

      [laughs]

    23. SP

      Um, but, like, some things are gonna be good.

    24. DA

      Jev everything is pretty funny.

    25. SP

      Yeah.

    26. DA

      Uh, it's a pretty funny way of doing it, saying it. Um, the-

    27. SP

      Yeah

    28. DA

      ... so I'll tell you the truth.

    29. SP

      Yeah.

    30. DA

      Um, the truth is that this is an empirical problem, just like scaling laws are, are an empirical thing. You know, like, why doesn't, like, robotics really work right now despite all the money being spent on it?

  15. 1:34:50 – 1:40:17

    Computer Use, Dark Data, and Jev’s Biggest Use Cases

    1. SP

      stuff.

    2. DA

      Whoa.

    3. SP

      Is this, is this what you were referencing?

    4. DA

      I've never seen... I haven't... I- I've seen... [inhales] I saw, like, a airline browser use thing.

    5. SP

      And, um, inside this new note, let's make the title say hello.

    6. DA

      Wow.

    7. SP

      Great. Great. Okay. Um, let's move on, and can you open the Arc Browser? And once you're there, can you Google search Norbert Wiener? Um, now can you open up x.com? Is this this kind of use case?

    8. DA

      Oh, the voice use cases. This is actually the first one I've seen. This is-

    9. SP

      Oh, okay.

    10. DA

      Wow.

    11. SP

      [laughs]

    12. DA

      Oh, wait, wait, wait, wait. Oh, like, can you go, can you go back a second? Can you go back a second?

    13. SP

      Um...

    14. DA

      Rumors claim Anthropic engineers wor- worship Claude as God. Wow.

    15. SP

      [laughs]

    16. DA

      Wow. Dang. That's pretty funny. Um...

    17. SP

      And here you are building prod.

    18. DA

      [laughs] Abso... Wow, this is sick.

    19. SP

      Uh, yeah, so, so c- clearly you can operate the whole computer with voice, with Jev as a decision model.

    20. DA

      So just like I'm anti-benchmarking, I'm also anti demos. I want to make sure that it works reliably. I love people are playing with it. This is super fucking sick, have no doubt. I want to see this. I wanna see it be used. I want our team to play with it. I wanna find the weaknesses, and I wanna solve that.

    21. SP

      Yeah.

    22. DA

      And I would lo... Man, that looked really cool.

    23. SP

      [laughs]

    24. DA

      That looked really cool. I want that.

    25. SP

      Uh-

    26. DA

      I want that. Like, when my, when my wrists are sore, I, like, just whp- whisper flow everything. That'd be sick.

    27. SP

      Well, as, uh, well, you know, just, just to round out the use cases side-

    28. DA

      Yeah

    29. SP

      ... 'cause I, I do have to let you go.

    30. DA

      [laughs]

  16. 1:40:17 – 1:42:29

    How Jev Could Reshape Coding Agents

    1. DA

      Um, Claude Code and Codex are, I believe, the, the winner, like the, the number one and two. I'm not entirely sure. I don't follow closely.

    2. SP

      Roughly.

    3. DA

      But like it's roughly that. But they're built around a single model world. You know, like, and, and that makes a lot of sense for them, right? Because, like, it has been a one-model game where it's like kind of like the same model but different intelligence that you're shopping.

    4. SP

      Mm-hmm.

    5. DA

      But all the open coding agents are like fucking jazzed right now because they're like getting their Jev on and-

    6. SP

      [laughs]

    7. DA

      ... like the thing is there's-- I'm sure they're trying a lot of weird stuff.

    8. SP

      Mm-hmm.

    9. DA

      But all the coding agents are kind of roughly at like approximate parity, right? Because, like, there's not so much you can do with a while loop. But the moment one person finds one killer use case that, you know, you can only do with that coding agent, everyone will flock to it because they have like a monopoly on that thing. But all the open coding agents will be able to copy that, right? The end. But I don't know what the Claude Codes and Codexes will do because they are built around that one model world.

    10. SP

      Single model, yeah.

    11. DA

      And like I think that's gonna be like a really interesting thing. You know, like I would love to be able to integrate with them personally. Like, I want to integrate with everyone. Like, uh, they, they might make competitors eventually, I don't know. But like it is not me, my job as Sonfire Infrastructure to be opinionated on that, right? Like, I want to just serve the world. Um, but I, I don't know if they would do that and like I think it'll make the coding agent game super weird. You know? Like, I'm so excited for that. Uh, and like I'm sure, uh, I'm getting my team to review right now an internal document I made on design patterns I suspect will be useful for coding agents, so hopefully I can share it like right after I walk home. Um, uh, but like I think that there's just like such ripe area for exploration out in the world and like it's, it's-- Man, if I did not have this, I would love to experiment with coding agents right now.

    12. SP

      Yeah. I mean, and, and I'm sure the coding agent companies would love to work with you as well to, to figure that out. Um, yeah, I, I do think that there's still use cases for Claude Code and Codex with you guys-

    13. DA

      Of course

    14. SP

      ... um, which, um, uh, it's, it's easy to explore there. Um, okay. I mean, you know, we've, you've, you've been very, um, uh, obliging and sort of indulging in all these, all these things. I just wanna take you out of TypeSafe-

  17. 1:42:29 – 1:49:32

    AI Safety, Frontier Pacing, and the Limits of RLVR

    1. DA

      Hell yeah

    2. SP

      ... just generally about... And you've, you've made very clear your position on, on the state of AI. Uh, give you m-more room on the alignment safety side of things.

    3. DA

      Oh, uh, did I not-

    4. SP

      Oh

    5. DA

      ... talk about safety alignment at all?

    6. SP

      Oh, you did. You did.

    7. DA

      Oh, maybe I think I didn't. I think maybe I didn't.

    8. SP

      You did. Uh, I, I-

    9. DA

      Oh

    10. SP

      ... just like, you know, I, I think that there's, there's a lot of, uh, you have a lot of researcher discussions. We have this every-

    11. DA

      Of course

    12. SP

      ... every NeurIPS.

    13. DA

      Yeah.

    14. SP

      What are people talking about? You know? Like, uh, so for example, um, I, uh, recently was at, uh, one of these researcher gatherings, and people are genuinely worried about the pacing, right? Like this, this whole topic about like we should slow down because-

    15. DA

      Mm-hmm

    16. SP

      ... uh, the public is like clearly not ready. Um, and, uh, I'm sure you have strong feelings.

    17. DA

      Um, I feel like this is the kind of thing that is a dangerous topic-

    18. SP

      Okay

    19. DA

      ... to talk about. Um, I'm happy to talk about it. I, I live for danger. [both laughing]

    20. SP

      All right.

    21. DA

      Our company brand is chaos. It's not Jev. It is irreverence and chaos.

    22. SP

      And you know, yeah. And, and like you were at OpenAI during like the one of the very first like- Very visible incident, just the blip, right?

    23. DA

      Oh, the- the-

    24. SP

      Which, like, and, and, like, you, the dominoes have gone down now-

    25. DA

      Mm-hmm

    26. SP

      ... to now every frontier lab has co-signed a document saying that they want to pace

    27. DA

      Um, interesting. I-- So comp- it's a very complicated, nuanced thing. I actually do want to write a response to this more formally. I do have, like, a little bit of a short version of my response-

    28. SP

      Yeah

    29. DA

      ... which is that, um, as you RLVR more, like RLVR is like, the, so RLVR is not actually about verifiable rewards. Like, that has been failing since before the reasoning revolution. Like, like, like, and that's the weird part about tasks, right? Like back when-- Oh, fun history. Back when RLHF was becoming a thring, thing, there were three different things that, like, are now called post-training, different efforts, and instruction following was by far the, like, the, the bastard child. Like, people didn't like it. They didn't want to take it into account. It was annoying. You know, like, I talked to the pre-training team, and I'm like, "Guys, this is the magic." And they're like, "We'd run so many model sweeps. You want us to wait for human evals to figure out which models to use?"

    30. SP

      [chuckles]

  18. 1:49:32 – 1:56:48

    Why Diogo Wouldn’t Pre-Train with $1 Billion

    1. SP

      [laughs]

    2. DA

      I mean, like, it's, it's, it's like, you know, it's a cost-saving thing.

    3. SP

      Yeah.

    4. DA

      You know, instead of, like, having to pre-train again. Like, there's intriguing stuff. I actually think that Like, intelligence has a je ne sais quoi at every single level, and it's always super-duper fascinating. Like, I am a shape rotator, so I don't like finding that, but I love it when people find it and teach me about it. Um, but in it, you know, looking at the data, this thing that, uh, our data team is so good at that I'm not, um-

    5. SP

      Hmm

    6. DA

      ... I, it's-- I find it really, really fascinating. I love actually thinking about, like, how capabilities are, like, put into the model, like, over, like, the short term. You know, like, there's, like, the, the, the, the really rapid alignment of fine-tuning, and over the long term, after seeing it over and over and over again. Like, this stuff gets baked deeper and deeper and deeper and deeper into the model until it gets robust. You know, and that is, like, the, the North Star to surface, and, like, the system one stuff is the stuff that ends up getting robust. So I find mid-training to be, like, a fascinating thing. Um, I'm a fan of all forms of training. Uh, I'm a fan of all forms of, like, surfacing new types of intelligence. I wouldn't do it all myself because it's expensive. Um, and I have said privately and also... Should I say this?

    7. SP

      [laughs]

    8. DA

      Huh. Huh. You know, like, my philosophy is anything I sh- I, I should say in, like, private with, like, an investor, I should say in public with the people because that is, like-

    9. SP

      Power to the people

    10. DA

      ... my thing.

    11. SP

      Yeah.

    12. DA

      Yes. So m- the thing I've said, uh, before is if you gave me a billion dollars, I wouldn't pre-train. Um, I still believe that to be true. It is a very expensive thing when if you are, like, like, if you're an AI engineer, you can, like, slice and dice and do all sorts of stuff. You know, like, Frankensteining is not the most elegant, beautiful thing, but it solves problems, baby.

    13. SP

      Hmm.

    14. DA

      So, um, anything except pre-training.

    15. SP

      Hmm. Hmm. Yeah. Uh, amazing. Uh, yeah, I, I think one, one direction that I do think that is interesting, uh, just, like, synthesizing all your, all your commentary about these model things is, like, do we have a, a, a, a, a super model, uh, that has all these capabilities involved, or do we break them out, uh, in, uh, fur-further? I guess sort of like, um, uh, one way to put this is that OpenAI was trending the direction of the omni model.

    16. DA

      Mm-hmm.

    17. SP

      Right? Um, 4.0 was, was one of those. Uh, then for, for, for a f- brief period of time, there was always, like, there was, like, a kind of a main branch of the, this is the chat tune model, and this is the coding tune model.

    18. DA

      Those are t- completely different things. Those are extremely different concepts. I would like break that down a little bit. So multi-modality is a little bit different-

    19. SP

      Hmm

    20. DA

      ... um, because sometimes the other modalities help, sometimes they hurt.

    21. SP

      Yes.

    22. DA

      Like, you know, people are moving-- They seem to be moving away from speech, which is different than audio, um, because it seems to not generalize well to the other stuff.

    23. SP

      Hmm.

    24. DA

      This might get solved. I'm a fan of all of this. But these are, like, empirical real questions. Like, scaling laws are not about just throw money at it and it gets good. Scaling laws are pragmatically how good is a thing, you know? Like, uh, like, there are worlds where, like, no matter what you scale, it may not be good enough. So, um, y-y, you know, like, computer use is not currently solved is my understanding. Like, I'm hoping that we can be a, like, play a part in solving that. But, like, it-- there might be no amount of data we collect that will solve that. We might need better methods or something else like that. So, um, like, we-- you need to be, like, really practical in all of this. Am I a fan of omni models? I'm a fan of all forms of intelligence. But I will go straight into one thing you talked about, which is different from pre-training, which is post-training-

    25. SP

      Hmm

    26. DA

      ... because I hate fracturing intelligence. That is, like, the bad thing to me, and this whole, like, chat first reasoning mode is because, um, it forces the intelligence to be fractured. Like, when you're optimizing for chat, this tends to be, like, pure RLHF, and it's quite intrinsic in RLHF to do the stuff people, like, naturally complain about, right? Like, oh, I'm gonna-

    27. SP

      You're absolutely right. And-

    28. DA

      Yeah

    29. SP

      ... you know.

    30. DA

      Psychophancy? Psychophancy? I don't-

  19. 1:56:48 – 2:03:10

    The OpenAI Story Behind TypeSafe

    1. DA

      Hell yeah

    2. SP

      ... because I, I do want to, uh, g-get you out. Uh, one is like, just reflecting on your two-year journey. It's roughly two years? Two point something?

    3. DA

      Um, with the company-

    4. SP

      Yeah

    5. DA

      ... I think that this is, like, more like a four-year journey.

    6. SP

      Yeah.

    7. DA

      But-

    8. SP

      Well, yeah. Actually, like, uh, I was thinking, remembering that, like, you had this, like, hero run around Thanksgiving. You were like, you were canceling everything because, uh, you were like, "Guys," like, uh, "everyone's on holiday. I'm gonna take all the OpenAI GPUs and g-go do this thing."

    9. DA

      Yeah.

    10. SP

      [laughs]

    11. DA

      That was a good time.

    12. SP

      And that was, like, the, the pre-TypeSafe-

    13. DA

      Yeah, yeah, yeah

    14. SP

      ... moment, right?

    15. DA

      I-- That might've been-- Was that when the coup was happening? I don't really know.

    16. SP

      Yes, actually. [laughs]

    17. DA

      Yeah, yeah, yeah. That sounds right. Yeah.

    18. SP

      [laughs]

    19. DA

      I remember. Oh, my God. I don't wanna... I, I'm not-- I, I don't think I have the time to spill the tea about the coup right now, but, um, that was really annoying. Um-

    20. SP

      The, the coup was annoying or the, the run was annoying?

    21. DA

      The, the coup was annoying.

    22. SP

      The coup. Okay.

    23. DA

      Yeah, yeah, yeah.

    24. SP

      Yeah.

    25. DA

      Uh, it... I will-

    26. SP

      Safetyists took over the company. Yeah. Anyway.

    27. DA

      Maybe next time we chat-

    28. SP

      Okay. All right, all right

    29. DA

      ... I'll dump tea about-

    30. SP

      Tea

  20. 2:03:10 – 2:09:29

    Why Diogo Thinks Most Neo-Labs Are Getting AI Wrong

    1. DA

      Oh, yeah.

    2. SP

      And another question is, someone like you-

    3. DA

      Yeah

    4. SP

      ... is in the frontier lab right now who is frustrated not getting the, the funding or the, the resources, whatever, uh, the attention. Uh, what's your advice to them? You know, do, should they do what you did?

    5. DA

      Should they do it? Ooh, that's a fascinating question. Um, man, how do I do this without burning bridges?

    6. SP

      [laughs]

    7. DA

      Um, I-- my sense is that most n- unless there's some level of economics I don't really understand, um, I think most neo-labs are crap. Um, I, I don't want to see myself with that as peers. Um, like I, I don't really understand what's going on there. Like, is it becau- like number one, I don't really value researchers. Um, I value people who, like, like look at my bitterest lesson, right?

    8. SP

      The data, the task.

    9. DA

      I, I, I want-- well, not just that.

    10. SP

      Yeah.

    11. DA

      I, like, we need researchers, but we need them to give a lot of fucks about the right task, and that's the important thing, right? So it's actually, like the, it's, it's kind of backwards when people value pure research pedigree 'cause that generally doesn't create value. Um, so it, li-like number one, I, the, I believe in North Star tasks and doing cool, really useful stuff. Um, number two, um, because I don't value researchers, I don't, I don't recommend going the... Well, it clearly is profitable for someone, or it might be in this environment. So, like from a purely pragmatic perspective, I don't see creating neo-labs as want, something that creates value. It seems to destroy value because, like, they are, like, redoing work from scratch with, like, low probability of actually moving the frontier, and as far as I've talked to most neo-labs, they don't really have a direction. They tend to want money to play around with their experiments. Um, if they have direction, I'm super in favor of it, to be clear. So my advice for someone is it really depends on why you're doing it. You know? If you are a researcher who wants to play a-around with research, um, probably the labs are the best place to do that, TBH. Like, there might be other places. I, I, I don't really keep track of that politics. But I would just recommend not being that way personally. You know, like, I think it's better for the world with people being driven to solve real problems. Uh, and those problems may be exploratory, that's fine, but, like, ideally have principles that you stand behind. But if you think that you wanna do the right task, like abso-fucking-lutely, like please do. Like, please break this, like, unimind, you know, uni-unimodal, like-

    12. SP

      Hive mind.

    13. DA

      Yeah, exactly.

    14. SP

      Yeah.

    15. DA

      Like, like ev- you know, like again, this pacing the frontier is coming from, like, this one view of AI that looks like, you know, AI super genius that is incredibly jagged. And that is, um-

    16. SP

      Solvable

    17. DA

      ... you know, it's solvable, and it's weird, and it's, like, not matching reality. And, um, it, it's like, it's tragic, right? Like, like I, I, I think, like, all of these, uh, like the, like really unearthing technology I think is, like, just good.

    18. SP

      Yeah. For what it's worth, uh, you know, a-again, I, I'm trying to rep-accurately represent the position of the, uh, anthropic OpenAI folks I was talking to, SpaceX as well, by the way-

    19. DA

      Okay

    20. SP

      ... uh, is that, uh, it is, this is a political thing much more so than a pure X risk thing.

    21. DA

      Yep.

    22. SP

      Uh, so yeah.

    23. DA

      Cool, cool.

    24. SP

      Political positioning is-

    25. DA

      And, and that, and that's beyond my pay grade.

    26. SP

      Exactly. Yeah.

    27. DA

      That's well beyond my pay grade.

    28. SP

      Once they sh- once they told me that, I was like, "I get it. Uh, this is about the twenty twenty-eight, uh, election." [laughs]

    29. DA

      Oh, no.

    30. SP

      Yeah. [laughs]

  21. 2:09:29 – 2:21:59

    Coding Agents Beyond the KV Cache and the Multi-Agent Future

    1. SP

      and cheap.

    2. DA

      Yeah.

    3. SP

      What is a second or third one that you wanna throw as a bone to someone else that you're not, that you want someone else to work on that you're not gonna work on?

    4. DA

      Ooh.

    5. SP

      Like, uh, just basically give people tasks.

    6. DA

      Give people tasks?

    7. SP

      Yeah, like, that your tasks, you-

    8. DA

      Oh, there's so many I want. Oh, what?

    9. SP

      You have picked your tasks, right? You know what I mean?

    10. DA

      What? Wait, I-- That's such a good question. Holy crap. Oh man, I'm so excited by that.

    11. SP

      'Cause you're, you're gonna be, you'll be f- so the next, like, 50 years, you're gonna be busy doing your thing.

    12. DA

      Hell yeah. Okay.

    13. SP

      [laughs]

    14. DA

      So let me give, like, a fun one and a not fun, uh, l- l- and, like, maybe a valuable one that's also fun. Um, my, my fun one is I think games could be so freaking cool if they were intelligent. Like, when I see people play around with, like, like Ali's Doom demo where, where, like, you can, like, get NPCs to control stuff, like, you know, like, like that was just really, like the-

    15. SP

      Yeah

    16. DA

      ... like a proof of concept. I think some really cool stuff could be made. It looks really, really cool. You know, like, um, like, I, I'm a big Stardew Valley fan, you know, and, like, it's, it's really static and it's still compelling. Like, I feel like there's a lot of cool story that could happen. You don't need to call, like, Jev in the game loop. It's probably too expensive for that. But even, like, simple, like, state machines for NPCs, I think it could make, like, such a compelling world. Oh, man.

    17. SP

      Mm.

    18. DA

      Um, and man, a little sad that I can't work on these types of things.

    19. SP

      Yeah.

    20. DA

      My, my life path is a little bit set right now, and I'm, um, uh-

    21. SP

      Yeah, but you can call someone else to work on it.

    22. DA

      Yeah, yeah. That's cool.

    23. SP

      And then, and then you can, like-

    24. DA

      Yeah

    25. SP

      ... feedback on it.

    26. DA

      And, um, the thing that I would really, really like to explore is, like, coding agents free from the tyranny of the KV cache. Like, like, it might not be as good as true coding agents are, but I think there's just so many weird things to think about. Th- that, that's why I wrote the article, "KV Cache Rules Everything Around Me."

    27. SP

      Mm.

    28. DA

      Um, uh, believe it or not, I don't think anyone has used the phrase on the internet, "Cache rules everything around me," C-A-C-H-E, um, when I, when I Googled it. Um, so-

    29. SP

      Okay

    30. DA

      ... uh, like, I wrote this 'cause I wanted to tell people about, like, this is how coding agents w- agents work and how the KV cache works-

Episode duration: 2:22:21

In the uListen app, the transcript lights up word by word as you listen. Get uListen

Transcript of episode cFx9Z3ZXca0

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.