Skip to content
OpenAIOpenAI

Live from DevDay — the OpenAI Podcast Ep. 7

The OpenAI Podcast is live for the first time. Host Andrew Mayne sits down with startups Cursor, Abridge, SchoolAI, and Jam.dev—each reimagining how AI can transform their industries. From healthcare and education to coding and collaboration, we explore how these builders are putting AI to work in the real world. Subscribe to the OpenAI Podcast on Spotify and Apple Podcasts

Andrew Maynehost
Oct 6, 20251h 1mWatch on YouTube ↗

EVERY SPOKEN WORD

  1. 0:000:09

    Intro

    1. AM

      [upbeat music]

  2. 0:090:43

    DevDay kick-off: Building AI products with real-world stakes

    1. AM

      Welcome to the OpenAI Podcast, where we're live from OpenAI DevDay. Here sitting with me from SchoolAI is Caleb Hicks. Caleb, hello.

    2. SP

      Hi, thanks for having me. This will be fun.

    3. AM

      So, Caleb, you're working on tools for helping educators and helping people, uh, basically in the classroom understand progress of students?

    4. SP

      That's right, yeah.

    5. AM

      So first off, what was your reaction so far to DevDay?

    6. SP

      Uh, a ton of fun, I think makes it... Uh, a, a, a lot of things to be excited about that help us build, but also help students and teachers be more creative as well, so that'll be fun.

  3. 0:431:06

    SchoolAI’s mission: Safe, managed AI tutors for students

    1. AM

      So what have you been working on over the last year? What has changed with AI that's accelerated what you've been doing?

    2. SP

      Ooh, um, I think probably the biggest advancement over the last year for us- so we, we, uh, put AI in students' hands. That's the main, uh, the main thing that we focus on, is safe, managed, uh, AI that can act as kind of one-time personal tutors for students.

    3. AM

      Mm-hmm.

  4. 1:062:35

    What changed in the last year: Model intelligence + cost improvements

    1. SP

      And so probably the biggest change from OpenAI has been model progression.

    2. AM

      Hmm.

    3. SP

      I think we get two advantages from that. One is, uh, significant leaps in intelligence.

    4. AM

      Mm-hmm.

    5. SP

      Uh, and the other one is, uh, you know, improvements in cost. Because we are working with, uh, an industry that isn't known for paying big dollars for software, uh, it's been important for us to be able to manage students using this in a cost-effective way. So those have been the two areas that AI progression has helped. From our work, it has been a lot of, uh, orchestration, which I'm sure we'll talk about a little bit.

    6. AM

      Mm-hmm.

    7. SP

      Just, just getting different AI agents and models to work together, uh, for the best outputs for students in particular.

    8. AM

      So a couple of the releases we saw today, one was the Agents SDK.

    9. SP

      Yeah.

    10. AM

      Now, and you've talked about that. How much have, one, tools changed the ability of, one, to work faster, and, two, the scope of what you find is capable now?

    11. SP

      Yeah, I think we're seeing teams across industries work way faster-

    12. AM

      Mm

    13. SP

      ... and building better software because they've got kind of this always on expert, hyper-senior, uh, engineer next to them that they're pair programming with, right? And, uh, so we see that with our teams as well, and that just allows us to, to build better software faster, uh, and get it in the hands of teachers and students, which is what we're here to do.

  5. 2:354:02

    Educator adoption curve: From banning AI to teaching AI literacy

    1. AM

      What has been the biggest shift you've seen in talking to educators or people like that in regards to AI in general?

    2. SP

      Yeah, great question. So every teacher, school, and district is on a very similar journey. It starts with permission, right?

    3. AM

      Mm-hmm.

    4. SP

      Two-and-a-half years ago, it was everyone under the sun was just banning AI altogether.

    5. AM

      Right.

    6. SP

      Uh, we've, we've moved past that into productivity-

    7. AM

      Mm

    8. SP

      ... as teachers and, and school leaders realizing, "Hey, this helps me in my job."

    9. AM

      Mm-hmm.

    10. SP

      Uh, the leading schools are starting to get into that, that really important spot, which is recognizing that every student has to know how to use this stuff.

    11. AM

      Mm-hmm.

    12. SP

      If you're going into- if you're graduating from high school and you're competing for colleges or jobs and you are- don't know how to use AI yourself, um, you're at a severe disadvantage. So, um, most people are now orienting to, like, "Yeah, we have to teach this." Uh, we think there's a couple of special steps beyond those two, uh, where, where you get to better support students, the AI tutor in every kid's pocket, right? But we think that is... It's got to be classroom connected, it's got to know what you're doing in class, and it's got to know, um, you know, where you're trying to go and help you move that direction. Um, that last step we get really excited about is how you can put AI to work with teachers, uh, families at home, school leaders, kind of the system at large, uh, to really make school awesome for students.

  6. 4:026:45

    SchoolAI product stack: Dot, teacher tools, and real-time student dashboards

    1. AM

      Could you tell me a little bit about the kind of stack you're using from both the teacher-facing, student-facing back end, or what you're working on in that regard?

    2. SP

      Yeah. From, from the product side, we have kind of three different, uh, parts of the product that the, that students, teachers, and school leaders use.

    3. AM

      Mm-hmm.

    4. SP

      So there's, uh, kind of just a, a pretty basic, uh, AI assistant, right?

    5. AM

      Mm-hmm.

    6. SP

      Um, the, the, the GPT wrapper, as they say. [chuckles]

    7. AM

      Right. Right.

    8. SP

      Right? Uh, but, but tuned to use cases in schools. I think a big thing that we felt like was really important is teachers should never have to become prompt engineers.

    9. AM

      Right.

    10. SP

      Uh, so-

    11. AM

      You know I was a prompt engineer.

    12. SP

      Yes. [chuckles] Yeah, so, so we do a lot of that, uh, kind of extra orchestration-

    13. AM

      Mm

    14. SP

      ... uh, to, we essentially enrich every prompt that, that a teacher writes to get better output for them, for their, what they're teaching, uh, their grade level, all that stuff. Um, so there's, there's that. Uh, we call that Dot. It's a fun, little, blue-

    15. AM

      Okay

    16. SP

      ... animated character. Uh, and then we have tools. It's a form, you fill it out, and it gives you an output: a lesson plan, adapted reading content, uh, things like that. Those, we l- we like to call those the 101, like the-

    17. AM

      Mm

    18. SP

      ... the checkers-level features, that kind of table stakes that you've got to give to, to teachers for them to move from, "Can I even allow this?" to, "This is useful for me." Uh, but the special part is when you start, uh, doing kind of these one-time, guardrailed, safe, managed AI tutors that the teacher can create-

    19. AM

      Mm-hmm

    20. SP

      ... give to their students, students are interacting, and then the teacher gets a real-time dashboard of how the students are doing, what they're doing with the AI. And, uh, to make that very concrete, uh, the last five, 10 minutes of class, a teacher may give what's called an exit ticket to their students. Um, so they've got a recording of everything that they did during class that day, and it loads up and says, like, "Hey, how'd the content go today?"... and it does almost a, what's called a, a formative quiz. It, it asks them questions, and then it's coaching them on the ans- uh, on, on what they learned, what they want to learn, where they might go next, tease them up for whatever homework they might have. Um, and then it will do just kind of an emoti- a, a kind of a social, emotional check-in. It will say like-

    21. AM

      Mm

    22. SP

      ... "Hey, how, like, how was class? Um, what feedback do you have for the teacher? Uh, what are, what are you looking for out of using this content?" And rolling all of that up to the teacher so that they know how to better support those students in the future. Um, a thing a lot of us don't recognize about teachers is they might be working with 300 students at a time.

    23. AM

      Mm-hmm.

  7. 6:458:41

    Classroom reality and the “GPS for impact” idea

    1. SP

      I had 42 desks in my classroom when I was a teacher.

    2. AM

      So you started off as a teacher before all this-

    3. SP

      I did

    4. AM

      ... that informed a lot of what you're doing.

    5. SP

      Yeah, yeah. So I had 42 desks in my classroom, and I was teaching seven or eight periods a day.

    6. AM

      Mm.

    7. SP

      Every day, teachers have to make this impossible choice: Do I work with, uh, the top 10% of students who love this, they get it, they want more of it, they'd stay after school if I let them; the 10% of students that are really struggling, maybe that's because they don't understand it, maybe it's a learning disability, maybe it're a problem at home, maybe they got bullied in the last class, or everyone else?

    8. AM

      Mm-hmm.

    9. SP

      And I care a lot about that everyone else, that middle 80%-

    10. AM

      Yeah

    11. SP

      ... because I was one of those students, and most of us were, definitionally. And we think about what we're building, uh, and what we've been able to build with, with OpenAI and some of the tools that were announced today, we'll be able to do even more of, is, uh, give teachers almost a GPS for impact.

    12. AM

      Mm-hmm.

    13. SP

      Like, "These four students really need you today," and you can jump in and support those four students in a way that you maybe wouldn't have even known that they had a concern.

    14. AM

      That- it brings up a very, I think, interesting point. When I talk to developers, often people confuse the tools for the product.

    15. SP

      Mm-hmm.

    16. AM

      And what you have to do is you have to both understand the needs of the educator. That comes from you working in the classroom and your peers working at SchoolAI and understanding that.

    17. SP

      Yeah.

    18. AM

      And I think that's the thing you're able to bring to it, where you look at this and go, "This is a platform to build on top of it," and that's something where you've identified all these areas that you can bring into to specialize it and make it very custom what you're doing.

    19. SP

      Yeah. I think that's something exciting we saw today-

    20. AM

      Mm

    21. SP

      ... in, uh, in the announcements, was, uh, opportunities for, uh, people like me with subject matter expertise-

    22. AM

      Mm

    23. SP

      ... with that, that really know a domain and were able to build kind of with you all, uh, with OpenAI, not just on top of OpenAI-

    24. AM

      Mm-hmm

    25. SP

      ... which is, which is, a, a really cool unlock for a lot of people.

  8. 8:4113:48

    DevDay tooling for education: Agent Builder, MCP, and evals at scale

    1. AM

      What are you most excited about that you saw today?

    2. SP

      The Agent Builder, for sure.

    3. AM

      Agent Builder?

    4. SP

      Yeah.

    5. AM

      Yeah. Yeah, that looks like, uh, it could be a lot of fun. And going back to when w- you know, you, you know how it was when you first started, you had to just wire up a lot of that yourself-

    6. SP

      Yep

    7. AM

      ... and code tools certainly make that easier, but just being able to drag and drop, think something like file search, the permission structure seemed really well thought out, and particularly what you're doing in a classroom situation-

    8. SP

      Yeah

    9. AM

      ... where you really have to have those safeguards in there.

    10. SP

      Yeah. Uh, we actually built our own-

    11. AM

      Really?

    12. SP

      ... and have for a number of years, and I think we're excited to go and get our hands on, on it and see what do we get to get rid of [chuckles] -

    13. AM

      Yeah

    14. SP

      ... what do we get to, uh, make even better now that we have access to it ourselves, um, o- o- or, or from you all? I think that's, uh... Either way, we're gonna learn a lot from working with it-

    15. AM

      Yeah

    16. SP

      ... and, and that makes it easier for us to use, but also, again, bring it into the hands of these people that aren't technical. They're not developers. They're not, they're not thinking about, you know, which model they're using, but they just want to get their stuff done.

    17. AM

      Yeah, I think that's a great point in that the more you can have the people who will understand who your customer is, in this case, students and teachers, understand what that problem is in less time, they're spending time to wire things up and run, you know, fast API servers and stuff to do this-

    18. SP

      [chuckles]

    19. AM

      ... seems like it can make the produ- product get a lot better faster.

    20. SP

      Absolutely.

    21. AM

      What else have you been excited about that you've seen?

    22. SP

      Um, I think, uh, we've, we've built some similar things, and in our product, we have this concept called power-ups, which are-

    23. AM

      Mm

    24. SP

      ... basically apps that you can use with Dot, our, our character.

    25. AM

      Mm-hmm.

    26. SP

      I think we got to see some good patterns and examples of that today with the new apps that were, that were announced, and I think f- one of the things we're really excited about is these partners that we've been developing, uh, that everyone is really solidified around MCP servers-

    27. AM

      Mm

    28. SP

      ... as a way to communicate with, uh, AI. And so, um, a thing that will definitely benefit us is OpenAI kind of drawing a line in the sand, saying, "We're doubling down on this."

    29. AM

      Yeah.

    30. SP

      Uh, and so now when we go to a partner that's already building for integration with ChatGPT, they can also bring that directly into SchoolAI, again, for that safe, managed, guardrailed experience-

  9. 13:4815:32

    Jam.dev introduces “Please Fix”: editing websites like a doc, shipping PRs automatically

    1. AM

      Caleb, hope you enjoy the rest of DevDay. So we're gonna be talking to a few other developers about some of their different experiences, and I'm always fascinated to see what it gets accelerated and how they're able to focus when a new tool comes out on really what is their core thing they're working on. So up next, we have Dani Grant, who's with Jam.dev, which is an in-browser tool for helping you evaluate your site and to figure out basically how to improve it. Is that correct?

    2. SP

      I'm so happy to be here.

    3. AM

      Great.

    4. SP

      And actually, later today on stage, we're gonna announce a brand-new tool.

    5. AM

      Oh, boy!

    6. SP

      It lets any PM, designer, marketer... Oh, I'm a little short, aren't I? [chuckles]

    7. AM

      You're good. No, no, no. Microphone's too tall. It's all good.

    8. SP

      I agree. Um, well, just like you just did, it helps anyone fix what's broken instantly without writing code. Um, it's called Please Fix.

    9. AM

      Okay. So I would use this, like my website, go into it and say, just, "Please fix," or?

    10. SP

      Yeah, I mean, like, yesterday, before [chuckles] this tool was announced-

    11. AM

      Right

    12. SP

      ... um, if you wanted to change, like, some copy on your site or, like, a, like, a button didn't look good or missed a hover state, you'd have to probably ask an engineer to do that for you.

    13. AM

      Right.

    14. SP

      And the engineer would-

    15. AM

      Nobody wants to do that. Nobody wants to do that.

    16. SP

      Yeah, they're like, "Okay."

    17. AM

      No.

    18. SP

      And then they'd be like, "Can you make a ticket?" You'd be like-

    19. AM

      Yeah

    20. SP

      ... "Okay," you know? [chuckles] And then the pri- the ticket gets prioritized-

    21. AM

      Yeah

    22. SP

      ... and then, like, maybe they get to it.

    23. AM

      I worked for a company, I won't name it, where we joked it was easier to release a model than put up a blog post.

    24. SP

      That's hilarious.

    25. AM

      Yeah. Won't name it.

    26. SP

      Um-

    27. AM

      Yeah

    28. SP

      ... well, so, so now, as of today, what you can do is, while you're looking at your site, you click on the Please Fix browser extension-

    29. AM

      Wow

    30. SP

      ... and then it lets you edit your site right there, like it's a Google Doc, like it's a Figma. And then when you're ready and you like how it looks, you just click Submit, and it creates the PR for you.

  10. 15:3218:35

    A new web paradigm: apps inside ChatGPT and “read, write, think”

    1. AM

      Very cool. What were you most excited about what you saw today?

    2. SP

      I mean, I think we just saw a new way to browse the web. Like, I think OpenAI maybe just changed what we mean by the web, what we mean by a browser. Like, if you think, like, Web1 is read, Web2 is read, write... Okay, there's Web3.

    3. AM

      Mm-hmm.

    4. SP

      And then maybe this is, like, Web4, like, read, write, think. I think we just saw a whole new way of experiencing the web, where it's a lot less mechanical, and it's a lot more stream of consciousness.

    5. AM

      So yeah, talk about the apps inside ChatGPT, right?

    6. SP

      It's freaking cool! [chuckles]

    7. AM

      Yeah, it is. It's... It makes you think a lot about when you're building something, what the core functionality is, like, what the purpose of it is, and the idea that if it's going to be presented inside ChatGPT. And so watching the demo where they interacted with, with the Zillow website and actually having to have data about that and be able to drill down into it, and it's, it's exciting to think about the possibilities there. And so I could see for you all, that seems like a pretty interesting area because people, as they focus on usability, they're gonna want to make sure those things work really well.

    8. SP

      Yeah, like, now when you build your inside-of-ChatGPT app-

    9. AM

      Mm-hmm

    10. SP

      ... if you're the PM, if you're the designer, and you want to tweak some things and make, make the app look a little nicer, you can just use our browser extension, change it from the ChatGPT interface-

    11. AM

      Mm

    12. SP

      ... and make the PR in GitHub. It's so cool. And I think, you know, these tiny tweaks, they often don't get prioritized today, but they should.

    13. AM

      Mm-hmm.

    14. SP

      Because the difference between a fine design product and a well-designed product is that the well-designed product changes the world. Like, the iPhone changes the world because it's usable, and there were actually attempts before that, that I won't name, that many people under the age of 30 have never heard of, um, because they just, they didn't have that attention to detail.

    15. AM

      Mm-hmm. Have you seen your development process change with tools that have been coming out, particularly AI tools?

    16. SP

      Yeah, I mean, I... Like, I'm biased. We're- we've been using Please Fix as we've been building Please Fix.

    17. AM

      Mm-hmm.

    18. SP

      And it, like, even today, our pricing page changed dramatically because a PM could just go in and test a bunch of stuff without asking an engineer. I think the thing I'm most excited about is this idea that you can move as fast as your entire creative team altogether, like, no disruptions for engineers. It's like people can move without having to have bottlenecks on a few people.

    19. AM

      So it seems kind of cool because what we're talking about is the idea that people who aren't specifically engineer background are able to make those changes, and has that been something you've seen basically within your company, the adoption of tools like Vibe Code and stuff like this for people to contribute and be able to come up with ideas?

    20. SP

      Yeah, it's really cool. Um-... when we, we talk to our users every day, and some of the stories we hear are awesome. Like, last week we talked to a user who's a firefighter, and building software for firefighters. That's cool.

    21. AM

      Mm.

    22. SP

      Um, talked to a user a couple weeks ago who, um, grew up in the church system and is building software for churches.

    23. AM

      Mm.

    24. SP

      Has no software experience, but is able to now make something that's very impactful to their community. I think that is awesome. I think we are about to see the Cambrian explosion of software, the same way that with the web, there's the Cambrian explosion of, like, news sources with, you know, Substack and Twitter. I, I think this is about to happen for software, and it's... I think it's one of the best things for humanity.

  11. 18:3523:29

    Jam.dev’s product philosophy: optimize for user “wow,” not just features

    1. AM

      So how do things work at Jam.dev as far as ideation, testing things with customers, releasing, and then figuring out what's best features and whatnot?

    2. SP

      The only thing we care about is, does this deliver a wow for our users when they use it?

    3. AM

      Mm-hmm.

    4. SP

      And so that's what we're focused on. There is an emotional response we want people to have when they use our product, because we work on the worst part of software development. Like, I don't know anyone who is like, "Today, I want to fix some bugs."

    5. AM

      Right.

    6. SP

      And so our job is just to make that whole part of the software experience a lot better, and so we're laser focused on that. We're just constantly talking to users. Every user that signs up from Jam hears from a co-founder. Every user who uses Jam hears from a PM. We are just co- in constant contact.

    7. AM

      When I worked at OpenAI, one of the most exciting things, and it sounds absolutely silly today, was when we watched GPT-3 spit out a React button. That was like, "Oh, my gosh, it could do..."

    8. SP

      I remember that.

    9. AM

      Yeah.

    10. SP

      I, I don't remember it inside, but I remember from the outside.

    11. AM

      Yeah.

    12. SP

      I remember seeing demos of that, being like, "The world just changed."

    13. AM

      That was, that was the threshold for us being impressed, was literally, like, four lines of code, and to be able to, "Oh, that's really cool, it can do that." What has been a big aha moment for you?

    14. SP

      I think... Look, it's, it's, it's similar to what you're saying, but when you think of what you just described-

    15. AM

      Mm

    16. SP

      ... coupled with what was just announced with the apps SDK, you can imagine that in the future, yes, humans are gonna be building a lot of apps-

    17. AM

      Mm

    18. SP

      ... that are shown dynamically as they browse the web, but also, I think that agents will dynamically build apps-

    19. AM

      Mm-hmm

    20. SP

      ... for you as you browse the web. And that opens up a whole world of possibilities, because you can have dynamic software right there. Like, imagine inside of an organization. Right now, if a PM wants to see how a product is doing, they have to build a dashboard, and it's a lot faster to do that today than even six months ago.

    21. AM

      Mm-hmm.

    22. SP

      But imagine the PM needs a dashboard, and they're in ChatGPT, and ChatGPT just gives it to them-

    23. AM

      Right

    24. SP

      ... and no human had to do that. It means that there are two types of software. There's sort of long-term software that humans are gonna work on. They're gonna, like, really fine-tune, make it great, like Zillow, Canva. And then there's going to be sort of disposable, one-time use software that an agent can just whip up, and that is just freaking cool.

    25. AM

      Yeah, it's, it's a thing where, you know, as a developer, you're used to sometimes spinning up a tool one time to use that, and then you're done with it. But it's another thing to think about that could be a new modality. You know, we get kind of fixated in sort of, like, the App Store sort of idea, and I think that there's gonna be, like you said, long-term stuff that you deploy inside of ChatGPT, but then the ability for somebody just to spin up a thing they're only gonna use once, and that's the end of it.

    26. SP

      Yeah.

    27. AM

      And have you seen, as far as things that sort of start off as hobby projects or things like that, or maybe inside Jam.dev, people have said, "Hey, I had this idea I wanted to solve for this thing," maybe even something from finance or comms or something, that's turned out to be something useful?

    28. SP

      Yesterday we were, um, at the rehearsal for our 10X codebase session. It's four startups. We're all demoing, and we're just sitting around, kind of backstage talking, and we're like, "Oh, how'd you start your startup?" And almost everyone, [chuckles] three out of four, I'm the only one, um, where their startup started as an internal tool at their company that they needed. And actually, these startups pivoted to the internal tool because they found it so tremendously valuable to how they build software.

    29. AM

      Well, that's, you know, how Slack got its start, and other companies. And it's a very interesting thing, where the thing you spend the most time on is often the thing that's gonna be the best product. And, you know, one of the things they talked about OpenAI on here today was, like, how 70% of the code's coming from, you know, the PRs are coming from, you know, generated by Codex. And it's a very interesting thing to see. When a company's using their own tool to build the tool, it seems to iterate much faster.

    30. SP

      It's actually so funny, because if you listen to standard startup advice, like, what would Paul, Paul Graham tell you? It's, "Hey, don't optimize the internal processes."

  12. 23:2925:59

    Future direction: self-improving agents via automated evals and prompt optimization

    1. AM

      What are you looking forward to? What kind of tools would you like to see that don't exist yet?

    2. SP

      Um, I... Well, I was, I was talking to the engineers sitting around me during the keynote.

    3. AM

      Mm-hmm.

    4. SP

      And they were really excited about the optimizer and the evals-

    5. AM

      Mm-hmm

    6. SP

      ... as part of the Agent Kit. And, um, and what they wanted to see was, well, like, what if the evals could be written automatically for you using your own data, and then use that to automatically optimize your prompt?

    7. AM

      Mm-hmm.

    8. SP

      So rather than people sort of sweating the details about these agents, what if the agents could improve themselves? And I think if we had that at Jam, like, we could move a lot faster, and we can make a lot more powerful software a lot sooner.

    9. AM

      Mm. Uh, what advice do you have to founders or developers right now?

    10. SP

      It's, it's never been a more fun time to build.

    11. AM

      Mm.

    12. SP

      I think we all just get to enjoy it.

    13. AM

      ... So how did you figure out that this was what your team wanted to work on, which Jam.dev? How did you decide this was the problem you wanted to solve?

    14. SP

      When, uh, my co-founder and I were product managers together at Cloudflare, we, we worked on the fastest moving team in the company. It's this sort of skunk works team that would try to do big, new things. It's the team that shipped Cloudflare Workers, um, their cloud compute platform.

    15. AM

      Mm-hmm.

    16. SP

      It shipped 1.1.1.1, which now fields a trillion DNS queries a month.

    17. AM

      Right.

    18. SP

      Um, and it was just trying to move fast on this team that we realized a lot of the frustrations and bottlenecks come from just reproducing issues, and there's no tooling out there. And no user, no PM, no one in sales knows how to communicate to an engineer what the engineer needs to know. And we're like, "We can't believe that there's no way to help the engineer get things done faster." We're spending all this, like, great brain time on communicating bugs, and hopping in calls, and screen sharing, and, and not enough on fixing them, and we thought, "That, that, that we can solve."

    19. AM

      It seems, uh, like a lot of things sort of in front of you as far as what you can do. How do you decide what you're gonna do next?

    20. SP

      Okay, I think, I think there's something that we t- under talk about in, like, startup world, which is if, if your startup works up- works out to your wildest dreams, you're gonna work on it for, like, 10 years.

    21. AM

      Right.

    22. SP

      And that's a really long time, and so you better just love the problem because that makes it really, really fun. And so I think you work on the thing where if you get to wake up every day, work on it, and talk to users of the thing, you're gonna be pretty darn happy about that.

    23. AM

      That's pretty awesome. Uh, how can people get started at Jam.dev?

    24. SP

      Jam.dev/pleasefix, and we'll please fix some code for you.

    25. AM

      Awesome. Thank you so much.

    26. SP

      Thank you!

  13. 25:5931:36

    Abridge’s core value: ambient documentation that gives doctors time back

    1. AM

      Uh, so it's been interesting to see what each kind of developer, what they're looking forward to, what kind of excites them as far as that. A lot of that's based upon what they've been working on. I know a lot of devs have to build a lot of internal tooling, and when you can solve for that with an SDK, it makes your life a lot easier 'cause you can focus on the thing you wanna work with. Up next, we have Zach Lipton, who is with Abridge. How you doing, Zach?

    2. SP

      Not too bad. How you doing?

    3. AM

      Fantastic. So Abridge, you're working on tools for helping the medical community, people who are doing, like, transcription and that kind of area. Is that... How would you describe it?

    4. SP

      It's an AI platform for doctor-patient conversations.

    5. AM

      Okay.

    6. SP

      Like, if we were to, like, rewind to, like, the state of affairs, you know, uh, post-adoption of electronic health records but pre-ambient listening, um, doctors were spending about two hours doing paperwork for every one hour of direct patient care. So there was this kind of, like, clerical, uh, burden crisis, um, and it was pulling- it was, it was a situation where technology was pulling doctors away from patients rather than bringing them closer.

    7. AM

      Mm-hmm.

    8. SP

      Um, what we do is we provide this platform that helps- kind of gives doctors superpowers, helps them with their paperwork, does all the note-taking in the background, preps them everything, so all these kind of documentation artifacts are ready for them the moment the visit's over in exactly the form they need, so they can be fully present with the patient instead of spending all their time staring at the computer.

    9. AM

      What kind of metrics do you have so far as far as, like, time saved for doctors?

    10. SP

      Sure. Interesting story, um, and a l- difficult to track down, in part because there's the time that doctors spend, uh, documenting during the day. But the reality of the status quo before was that most doctors actually didn't finish their notes during the workday. So they were home after hours, logging into the EHR and doing what we called, um, pajama time.

    11. AM

      Right.

    12. SP

      They're basically sitting there, like, pulled away from dinner with their families, or logged in after hours, you know, sitting in [chuckles] sitting in bed, finishing up their notes. Um, our reports, so we, we, we've cobbled together this information from a bunch of different sources, but we see doctors saving as much as an hour or more a day. Um, we see, you know, doctors- some doctors seeing, like, 10, 15 patients in a day.

    13. AM

      Wow!

    14. SP

      We're talking about, like, you know, five to 10 minutes often in note-taking, so it's a, it's a tremendous, um, kind of relief. But even beyond the, um, actual time saved, oftentimes there's an even larger sort of, like, perception of burden lift, and that's because the doctor's worrying about less and able to focus on their patient.

    15. AM

      Yeah, I mean, that's great 'cause, like, you, you know, look at with... An hour a day is either an hour they can spend with patients or just not have burnout and, you know, have more focus on that. You know, that's, it's- We were talking before SchoolAI and looking at how they're basically able to help teachers spend more time in the classroom with students, and that's the same problem you're dealing with here. How can doctors be there for students or, or excuse me, patients and also-

    16. SP

      Yeah.

    17. AM

      Yeah.

    18. SP

      Well, so we have a channel in Slack, and it's what we call Love Stories, and it's where we hear, like, uh, kind of, like, all the feedback from the field from doctors. And one of the, one of the wild indicators that, like, we had landed on something big, and this is relatively early, um, maybe like a couple months after we launched the first, like, enterprise pilot at a hospital system, was when we started getting stories coming in. And they weren't just talking about the clinical experience, but they were talking about, like: "Uh, I, I spent... Uh, I actually got to have dinner with my family every night this week for the first time in, like, 10 years," or, like, "Abridge is saving my marriage." And that was, that was not, like, where I was expecting-

    19. AM

      Wow

    20. SP

      ... things to land so quickly. But, uh, you know, the, the problem is that big.

    21. AM

      What did you see today at DevDay that has you excited?

    22. SP

      ... Oh, um, so many things, but maybe like two that are top of mind. Um, one, a lot of people have already talked about the agent developer kit.

    23. AM

      Mm-hmm.

    24. SP

      And I think that's just extremely exciting. There's this moment right now where I think everyone- it's sort of a proto-discipline.

    25. AM

      Mm-hmm.

    26. SP

      So everyone's been rolling their own tools in the hope of, like, kind of trying to figure out, like, what is the paradigm? How does this work? And there's so many things that have to work together. Um, there's the context engineering, there's the prototyping, there's the sanity checking, um, there's evaluation. There's also, down the road, you know, everything around production and monitoring.

    27. AM

      Mm-hmm.

    28. SP

      So I'm really excited to see where these tools, um, ultimately go. But seeing OpenAI, like, take a strong position and put a, a kind of comprehensive offering that brings together a lot of these things that, you know, people have been d- rolling their own orchestration tools, their own evaluation platforms, we certainly have. Um, and seeing how much, how much this is gonna create a common platform and allow us to sort of lift off and focus more on the content, um, is something I'm super excited about. Um, and then in general, I've just been extremely excited and drawn a lot of inspiration from all the work that's gone on in terms of software developer tooling.

    29. AM

      Mm-hmm.

    30. SP

      And so we are, we are developing AI-powered products for our customers, but we're also big consumers, as, uh, you know, productivity tools like Codex, um, um, play a big role for us, and just seeing how far we've come there. I mean, I remember, um... So my background is academia-

  14. 31:3644:07

    Healthcare-grade reliability: defining hallucinations, building eval pipelines, and earning trust

    1. AM

      So when you work in medical, it's a very high-stakes area, and so that's got to be something you, you think a lot about, about how you deal with hallucination and also how you deal with customer concerns about these things.

    2. SP

      Hundred percent.

    3. AM

      So what do you look forward to in tools? What have you seen the biggest help in that area?

    4. SP

      Um, that's an area where we've had to develop a lot of our own technology.

    5. AM

      Mm-hmm.

    6. SP

      Um, you know, what is a hallucination? It's kind of like, like, back in the old days-

    7. AM

      Mm

    8. SP

      ... of, like, developing simple classifiers, we had, we had false negatives and false positives.

    9. AM

      Yeah.

    10. SP

      And now, kind of like everything that's like... If, if it's there and you don't want it, it's a hallucination.

    11. AM

      Yeah.

    12. SP

      And the question is, well, what is a hallucination? Sometimes it's completely confabulated information that is asserting facts about the world that are not real. But in the context of medical note-taking, medical documentation, order placement, um, it's... There, there's, there's a kind of particular situated notion of what we really mean. It's something that's sort of unlicensed, uh, you know, by the, the sort of surrounding context, the substantiating evidence, even if it might be true.

    13. AM

      Mm-hmm.

    14. SP

      You know, if, uh, if a doctor doesn't, um... If, if a kind of explanation of a disease, like, shows up in a generated patient-facing summary that the doctor never said-

    15. AM

      Yeah

    16. SP

      ... you know, that's, that's kind of, like-

    17. AM

      Bad [chuckles]

    18. SP

      ... even if some of the information might be, like, either correct or plausible, like, that's not within our- So we have a kind of bespoke notion of what constitutes a hallucination.

    19. AM

      Mm.

    20. SP

      Um, but we are able to, like, kind of often draw a lot of inspiration from what can, like, the frontier models already do out of the box.

    21. AM

      Mm-hmm.

    22. SP

      Like, if we define our ontology of, like, these are the types of, of errors we're concerned with, then we can go and say: What is the ability of an out-of-the-box model, given, like, each, each documentation sort of sentence, à la carte, to correctly designate them as belonging to the right category? And we find, okay, we're already within the realm of, like, the model's able to judge, even if, even if it's not able to sort of never commit the crime in the first place, it's able to recognize when the crime's been committed. That gives us a sort of, like, proof of concept, and now what we need to do is make it better, more accurate, cheaper, faster. So ultimately, create our own special-purpose models that are able to take, in parallel, every single sentence in all the generated documentation and surrounding artifacts-

    23. AM

      Mm-hmm

    24. SP

      ... and process for each one, like, sort of, does it contain an error of, of, of a unacceptable variety? Like, of, of, of what kind? And then a kind of pipeline downstream for remediating. And we're able to do that, um, with about ninety-seven percent recall at this point.

    25. AM

      Cool. So do you have any advice for people who are trying to work on basically developing their own evals for hallucination, or just sort of a good starting point?

    26. SP

      I think it all starts with getting really crisp about what you really mean.

    27. AM

      Mm-hmm.

    28. SP

      And I think that's what we've seen before, is that what is a hallucination for us is a little bit different from what is a hallucination for, like, a general, um, sort of like open world QA system.

    29. AM

      Mm-hmm. So is there kind of like a, uh, boundary which you keep expanding? For instance, we talk about medical, say, "Okay, we feel maybe working in scribing right now is, is an area that we can probably solve for and produce a pretty good product that's at or better than human level." Then do you look at, like, there's areas which you would expand out to as you feel more confident?

    30. SP

      Absolutely. So for us, um, we've always bristled a little bit when, you know, like, VCs put up this chart, and they're like, "These guys over here are the, the conversation agents, and these guys here are doing- are the coding startups, and these guys are the scribing companies."

  15. 44:0746:22

    Cursor’s evolution: from autocomplete to autonomous coding agents (and why “vibes” matter)

    1. AM

      See you. It's interesting to see where you have companies that are dealing with very high-stakes stuff, like medical or education, and a lot of it is the trust building. It's not a thing where you just pop out with a product and you say, "Hey, we're ready! We're done." You can see from the examples here between Danny and Zach and how they have to basically... and, um, Caleb, of basically just trying to sort of show the customers one step at a time, iterate on the product, and improve it. And here to talk to us about tools for helping work on this is Lee Robinson from Cursor. How are you doing?

    2. SP

      I'm doing well. Thanks for having me.

    3. AM

      Lee, it is great to have you here. Uh, so Cursor.

    4. SP

      Mm-hmm.

    5. AM

      Um, I probably have about three Cursor windows open right now on my computer-

    6. SP

      [chuckles] Amazing

    7. AM

      ... that I'm thinking about right now. Uh, it has been an incredible product evolution for you all here. And just a little backstory: I was at OpenAI when we worked on the earliest version of Codex and code completions.

    8. SP

      Mm-hmm.

    9. AM

      And I kind of naively thought that, "Oh, well, I just ask, you know, GPT-3, the 3.5 at this time, or the Codex model or Da Vinci Code, whatever, and say, 'Just complete it,' and it's done, and I got my code." I'm like, "That's it. Code is solved with AI- [laughing] ... and we're done."

    10. SP

      Yep.

    11. AM

      Turned out that's not the case.

    12. SP

      Yeah, it turns out there's a lot that goes into it, especially from maybe simple text autocomplete, but to where we're at now with fully autonomous coding agents who can self-correct and fix their own errors and pull in information from the outside world, and it's wild how much better the coding with AI space has gotten just in the past year, I would say.

    13. AM

      Mm-hmm. And it's a tool very much... What I appreciate is the fact that you guys are using Cursor to make Cursor better.

    14. SP

      Definitely. Yeah, one part of our culture that I think helps us produce a better product is not only, of course, dogfooding how we build Cursor by all of our engineering teams, all of our design teams, product management teams, using the product and using Cursor Agent to build the actual experience-

    15. AM

      Mm-hmm

    16. SP

      ... and for every part of their daily work. But then it allows us to give not only hard evals and, you know, feels on how a model works, but just what it, what it feels like every day to use the product. You know, sometimes the feedback is, "This just didn't feel right. I don't know what it was with this model experience, but we, we need to tweak this a little bit here." And that is actually just as valuable as, you know, a, an eval that shows that maybe we need to tweak this number one little bit. So the vibes are, the vibes are important, too.

  16. 46:2249:49

    Shipping at Cursor: internal adoption as product-market fit + rapid model iteration

    1. AM

      How do things work internally as far as adding feature? I imagine when you're a company filled with developers, building a tool for developers, there's a lot of suggestions on what you should be doing, but how do you prioritize?

    2. SP

      Yeah, I think across the entire company, anyone has the ability to contribute features-

    3. AM

      Mm-hmm

    4. SP

      ... and we kind of measure if a feature gets product-market fit internally.

    5. AM

      Mm-hmm.

    6. SP

      So people make changes, they push them to main, and they see if it gets adoption. They kind of push it out to company Slack and say, "Hey, we built this feature. Um, here's what it's good for. We'd love for you to try it out." We've even seen people incentivize with bagels and other pastries- [laughing] ... to get people to try out the feature. And they get a lot of feedback internally on if it's good, whether they should change. We also have weekly demo sessions where people show off the cool things that they're working on. And some features don't work out.... and we end up removing them. And others, like, really take off. Like, people have been wanting this for a while. We build it internally. All of a sudden, there's-- we look at metrics, and we see how many internal devs are actually adopting the feature and what the churn rate is, and if it reaches a certain threshold, we have the conversation, "Maybe we should actually release this externally." So then we go through kind of a series of steps where it starts internal, then maybe rolls out to some of our ambassadors, rolls out to some of the people who opt in to our nightly channel, which is, like, you know, releases all the time, and then eventually, there's the path towards getting it out to everybody.

    7. AM

      So one of the challenges in AI now is evaluating models, and we can put something into one of the, the evals, one of the benches or whatever, but say, "Oh, it performs this well," but it's entirely different when you put it inside of an IDE, and you have to basically put a harness around it.

    8. SP

      Right.

    9. AM

      So how much time do you all have to spend really evaluating these things to really figure out if this is gonna be a good fit or not?

    10. SP

      Yeah, quite a bit. I mean, one of the things that, you know, we love working with OpenAI on is getting access to integrate the model early, work with your team on-

    11. AM

      Mm-hmm

    12. SP

      ... tweaking the prompts, getting the harness updated as newer model comes out. I know we spent a lot of time on this with GPT 5 to-- actually, we were able to delete some of our system prompt, where-

    13. AM

      Hmm

    14. SP

      ... as the models get better, you don't have to be as precise with the instructions that you're giving it, and the tools are getting better, too. So we, we spend a lot of time not only dogfooding and just trying it for a bunch of tasks internally, but also having many of the engineers internally all try to build new features on the core product experience with new models as they come out. So then you get a good range of, you know, maybe smaller tasks, but also real tricky engineering problems, like real gnarly bugs in a very large code base.

    15. AM

      Yeah, it's interesting in that, um, a couple years ago, people sort of wondered, like, what was gonna happen in the model space. Was everything gonna be using big foundational models, whatever? But you guys have sort of an all of the above.

    16. SP

      Mm-hmm.

    17. AM

      You're using... You can have-- I can use-- If I want, I can choose a variety of different models in there. I can use Codex, whatever, inside of there, but also, you guys are, like, training your own models for the smaller, for, like, tab completions.

    18. SP

      Yeah, it's been an interesting journey to watch. The first versions of Cursor were really focused just on code autocompletion-

    19. AM

      Mm-hmm

    20. SP

      ... and it was predicting the next line or maybe the next action.

    21. AM

      Mm-hmm.

    22. SP

      And now we kind of moved from a world of using an off-the-shelf model to training our own model for autocomplete, to now we do online reinforcement learning, where we can actually roll updates every thirty minutes to the model, which is pretty amazing, just based on the signals we get back from developers, whether they're accepting or rejecting changes that the autocomplete, um, suggests. And that's been really helpful, where you can have both these really focused and intentional models for very specific parts of tasks in coding, and then as you all make better models, these foundational models, we can integrate them and make that experience really great, too.

  17. 49:491:01:14

    New users, new workflows: agent-first interfaces, context practices, and the future of ‘vibe coding’

    1. AM

      I'm seeing more and more of my friends who never even thought about coding start off with writing something maybe in Canvas inside of ChatGPT, and then all of a sudden go, "Oh, how would I deploy this?" And then they go try Cursor and try to do this. And how much have you seen the demographic of the people using your tools change?

    2. SP

      Yeah, first and foremost, because we dogfood Cursor to build Cursor, like, we're always building for the professional software engineer-

    3. AM

      Mm

    4. SP

      ... and we're trying to make that experience really great. But as a side effect of making the product easier and more accessible for engineers, it kind of welcomes in this whole new generation of people who maybe were on the fringes of coding or had tried coding in the past, and now it's, it's much more accessible for them to do that. So a lot more product managers, a lot more designers. Uh, our support team uses Cursor quite a bit, and as more of these people have came in and started to use the product, it's allowed us to change actually some of the core features we're building. So one of the things that we're releasing right now is a new view of viewing the Cursor experience, where it's less like a traditional code editor-

    5. AM

      Mm-hmm

    6. SP

      ... and it's more about working with the agents. Because for a lot of people who haven't coded before, you open up an IDE, and you're like: What am I looking at? Like-

    7. AM

      It's a notepad, all this stuff. Yeah, I see.

    8. SP

      There's, like, all this file tree on the left-

    9. AM

      Yeah

    10. SP

      ... is very overwhelming for people who are just getting started, versus opening up something that looks closer to a ChatGPT. You're like, "Okay, I know this experience. I've got my agents on the left. I can type into my in-input text box," and so far, we've seen this really resonate with that type of persona, where they're graduating into becoming a developer.

    11. AM

      I went from somebody who was first copy-pasting before we even had ChatGPT from the playground or whatever, building some simple little custom tools, to then using the IDE, and like in case of the case, using Cursor and using tab completions, and now really just sitting down and saying, "I just need to write a really good agents.md or a really good description." Have you seen those patterns shift, you know?

    12. SP

      Yeah, I think as people get more advanced with working with coding agents, they really start to realize that high-quality context in is gonna give you much higher quality responses from the models, and we can build a lot of this into the core product itself. But some of it require... Just, it depends on your use case of what you're trying to build, the system requirements, and a lot of this stuff gets put into an agents.md file-

    13. AM

      Mm-hmm

    14. SP

      ... or gets put into newer features we have, like planning.

    15. AM

      Mm-hmm.

    16. SP

      So you can actually work through a plan mode, go back and forth with the agent to do some research on what you're trying to build, and it can search your code base and kind of help paint a picture, and then when you're handing it off to the model to do coding, it's already got all of this amazing input context, and the quality of the code generated is just significantly better at that point. So we've seen that be very helpful, too.

    17. AM

      What would you advise for best practices?

    18. SP

      [lips smack] For general just adopting Cursor?

    19. AM

      Starting there, yeah.

    20. SP

      Yeah. I think that for people who are completely fresh to using Cursor, and we'll start with more of the professional engineer use case, then we can talk about others, but for professional engineers, I think what we see for most people is their on-ramp is they start using the editor just like they would traditional editors or IDEs, where mostly they're using tab, and they're doing their normal coding-

    21. AM

      Mm

    22. SP

      ... and they're still getting AI suggestions as they write along, and they're using agent to somewhat augment that experience, but they're not coding maybe agent first.

    23. AM

      Mm-hmm.

    24. SP

      But I think slowly over time, as the models get better and the tools get better, they're graduating then into, "What would it look like if I can hand off more gnarly tasks to the agent to maybe run in the background or go refactor some part of the code base?" So I usually recommend that progression for professional engineers. It's kind of the inverse-

    25. AM

      Mm

    26. SP

      ... for those who are not professional engineers because it's very hard for them to drop into code and then know, "Okay, this is JavaScript. Oh, actually, this is TypeScript, and this is what a type is, and this is what all these fancy words mean." It's much easier for them to take the other approach, where they start with the agent view.

    27. AM

      Mm-hmm.

    28. SP

      They talk to the agent in natural language, and the agent outputs code, and then they can ask the agent, "What does that mean? What is a const versus a let?" You know, "What do these things mean?" And, you know... Or something in Python, for example. So generally, that's what I recommend.

    29. AM

      ... where do you think this is gonna be headed? We're, we're five years into GPT-3. You know, the first time I mentioned it earlier was that, you know, seeing somebody make a React button was exciting.

    30. SP

      Yeah.

Episode duration: 1:01:14

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Transcript of episode QIdUllqmuls

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.