Latent Space ↗ · 2026-11-09 05:41 · UTC+8
How Stanford Teaches AI-Native Engineering — Mihail Eric, Monaco
独立观察 Latent Space 原文语言:英文
What happens when students can one-shot last year’s homework? Inside CS146S and the engineering team at Monaco.
全文
Play video
Open video on YouTube ↗
The AI Engineer YouTube channel just crossed one million subscribers. Thank you to everyone who’s watched a talk, sent one to a teammate, or put something they learned into production. For this special, we wanted to sit down with someone who has to answer a question a lot of us are asking at work: what should a software engineer actually learn now?
Mihail Eric has two places to test his answer. He teaches The Modern Software Developer at Stanford and leads AI at Monaco, where his colleagues use coding agents to ship software and investigate outages. I asked him to take us through the syllabus, then tell us which parts survived contact with his own engineering team.
This is also meant as a preview for all of you joining us in San Francisco for AIE Code next week, as required knowledge for all the conversations with the speakers, sponsors and attendees you’re about to have. If you can see this as a LS subscriber and haven’t got a ticket yet, you can use this code for 30% off (no refunds, sorry)
Last year’s homework takes one prompt
The first run of CS146S had nine assignments and a capstone. In one exercise, students ran an AI code reviewer on a repo and evaluated its feedback. By the next run, Mihail figured students could one-shot a lot of those exercises. When he asked a room of Stanford sophomores and juniors how they coded, everyone he surveyed was already using an agent.
So this time, part of the homework is contributing to an open-source project. The person who maintains the repo reviews the student’s patch. I like what that does to the assignment. You can ask an agent to implement a feature in an afternoon. You still have to find out whether the maintainer wants it, why the code behaves the way it does, and what else your patch might break. That conversation is also how a junior engineer gets to learn from a senior one.
There’s an exercise in the episode you can borrow for your next PR. Geoffrey Litt’s explain-diff skill turns a change into a visual walkthrough, then quizzes you about it. Try it on a patch your agent just wrote. Which question do you have to reopen the code to answer? Watch the discussion.
What Monaco buys, and what it builds
At Monaco, the team evaluated code review products and kept using Devin. Agent workspaces went the other way. A background agent needs somewhere to run the product, reproduce a failure and test the patch. The details depend on how Monaco’s cloud is set up, so the team built its own workspaces. Mihail’s rule of thumb: “You buy to learn, and you build to keep.”
One result is Hal. An engineer can ask it to investigate something that broke and open a PR. A salesperson can ask the same system how the product works. In one case the useful answer is a change someone can review. In the other, it’s an explanation you can give a customer. Give both people a wall of debugging output and you’ve only served one of them.
The question I kept coming back to was what happens at the other end of the PR. An agent sees the current code. Where does it look to find out why the team rejected this same change six months ago? That takes us from Basis’s Authority Map to Mihail’s prediction that open-source repos will become agent-run software factories. It’s a good reason to send a student to a maintainer today. Someone still has to decide which change belongs in the project.
If you’re building with coding agents, come join us at AI Engineer CODE. And if you’ve been teaching this stuff yourself, I’d love to hear which assignment you had to rewrite first.
Show notes
Stanford CS146S — The ten-week syllabus, assignments and open-source partners. You can also switch to the previous year’s course to compare.
Build a coding agent and look inside Claude Code — Mihail’s walkthroughs of the tool loop and the harness around it.
Understanding is the new bottleneck — Geoffrey Litt’s approach to learning what changed in an AI-written diff.
Monaco’s agent-developer workspaces — The team’s reasoning for building a place where agents can run and test the app.
How to Kill the Code Review and the underlying Faros study — Teams with high AI adoption merged 98% more PRs, while their PR review time was 91% longer.
Basis’s Authority Map — Where an agent should look for current behavior, earlier decisions and intent.
Stripe’s Minions — A production example of giving background coding agents an environment and a path to an engineer-reviewed PR.
Boris Cherny’s Steps of AI Adoption — The five stages we pull up on screen near the end of the episode.
Mihail on The Thinking Mode — EO Studio’s interview, excerpted at the start of ours.
Timestamps
0:00 · One million AI Engineer subscribers and the CODE Summit
0:51 · Mihail Eric and Stanford CS146S
5:26 · What junior engineers need to learn now
10:02 · Open-source maintainers review the students’ code
15:04 · A tour of the ten-week syllabus
24:04 · The loop, tools and harness inside a coding agent
32:18 · Context engineering for a large codebase
38:15 · Skills that make you understand the diff
46:42 · The Monaco.com dispute and the airplane banner
50:23 · What Monaco does for sales teams
59:21 · Inside Monaco’s engineering team
1:01:40 · “You buy to learn, and you build to keep”
1:05:24 · Making repos agent-ready and closing the on-call loop
1:12:37 · When code review becomes the bottleneck
1:20:37 · Security, dependencies and permissions
1:30:13 · Background agents and Stripe’s Minions
1:34:16 · MCP portals and why infrastructure converges
1:41:22 · Building the software factory
1:45:24 · What work is left for developers?
1:52:16 · From personal adoption to team autonomy
Transcript
Download the complete text below. In the web edition, you can also read the transcript and click any timestamp to jump into the interview.
transcript.txt152.95 KB • PLAIN File
SponsoredYour sponsor ad hereReach the AI engineers building what comes next.
Latent Space is read by the people shipping agents, models and infrastructure. Enquire about sponsoring this slot.
business@latent.space →
Automated transcript, aligned to the final episode. Timestamps open the corresponding moment on YouTube.
0:00 swyx · Intro — Okay, this is a pretty special episode because we're celebrating 1 million subscribers on the AI Engineer YouTube channel. So go over there and subscribe if you haven't heard about it. The guest is Mihail Eric, who is not only teaching The Modern Software Developer at Stanford, which is going viral right now, for basically covering all the AI-native development best practices, but also he is head of AI in Monaco. So he's not only a teacher, but he's a practitioner.
0:24 And those of you coming to AI Engineer CODE Summit next week, it's going to be the celebration of all the extreme progress that you've seen in coding in the last year. I'm excited about all the themes of fighting slop, of system one models, and of increasing your ambition for major rewrites of basically everything that you've seen in code. There's never been a more exciting time to be an AI engineer. And with one million AI engineers, I think it's just getting started.
0:49 So let's get into the interview.
0:51 Okay, we're in the studio with Mihail Eric, adjunct professor at Stanford and head of AI at Monaco. Welcome. Thank you. I'm glad to be here. You caught our attention because of your course that you are refreshing for the third time, third time?
1:03 Second time. Second time. Yep. The CS146, or 146S, The Modern Software Developer at Stanford.
1:09 Mihail Eric · EO Studio excerpt — This particular generation of junior developers, of junior engineers, the people that are now entering the workforce, will, I think, be the first kind of generation of that new shift.
1:18 And I looked at the syllabus and I was like, this is everything we cover. So every now and then I like to invite people like yourself who like you cover a broad range of topics and then we can sort of go topic by topic and Give people the state of the art on each of these things, which I assume you're doing with all your guests anyway For sure. Tell us the history of the course.
1:36 What made you want to Spring out CS 146? Yeah, is the second time it's being taught and I I taught it for the first time last fall, so fall 2025. This was pre 4.5, 4.6 days. even before fall 2025, the course had been about a year in the making. The genesis of the class was probably November of 2024. And I had sort of had this idea that we're seeing all this stuff happening in coding agents, and yes, they were an earlier version of the coding agents, but already it felt like there was something drastically changing in terms of how developers were doing their work, quickly we were getting work done, all that fun stuff.
2:08 And so at the time, was all just scattered blog posts, scattered things you could find online if you were trying to get into the methodology of how to do these things. And so I had this idea like, hey, well, is there a way to kind of structure a curriculum around this that's a little bit more formal?
2:23 Had the idea, and my alma mater is Stanford, and I always had this to go back and teach something and kind of pay it forward. I've always been very deep into education. And talked to Chip who also taught a class one of my good friends Chip Yen yeah Chip exactly spoke to her she had taught her I guess designing machine learning systems and so like asked her what that process was like and sort of you know took a lot of inspiration from how she designed the curriculum and thought about you know getting something the school put it together spent about nine to ten months this was now fall of 2024 through to like you know mid to late of 2025 got it through the committee,
2:58 made a case for the class to exist, you know, had to put together a proposal and everything. And that took me to fall 2025 when I heard it for the first time, was very well received. know, students were really interested in it. There was even, I guess, like a Business Insider article that was written about the class last year. And then, yeah, this year, a lot of things changed. I would say really agents, autonomous coding agents, really picked up in a way that we had not seen before.
3:23 So it felt like it was time to do this again, refresh things, and then here we are. Meanwhile, you're also head of AI at Monaco, which is also a very buzzy startup. Yes, yes. We are in the airwaves right now and having a fun time doing it. Yeah, so I do like that you're also, I guess, a practitioner. You guys are obviously implementing all this stuff at Monaco. Yeah. Any, I guess, principles or observations about just have changed from last year to this year at a high level?
3:53 Yeah, yeah. a ton. I think that when I reflect on what last year's version of the class was, I mean, coding agents had been around, but we were still in kind of that phase where companies were emerging that were tackling every single part of, like, the AIS DLC. There was, like, a coding agent for code review. There was a coding agent for spec design. There was a coding agent for SRE. And, you know, some of those, of course, some of those companies still exist.
4:16 But it felt like last year it was a lot more about a broad tour of here's everywhere you can use coding agents. And in a way, a lot of the curriculum last year was geared toward exposure. And this kind of survey, this kind of like odyssey of sorts through, hey, everything that you knew ASDLC is now changing because of AI. This year, I think there's some principles that are solidifying, right?
4:38 The idea of like very careful context engineering, the idea of like really thinking through sort of like design and architecture as a way of handling really complex tasks. And so the nature of my class is it's not intended for the like beginner programmer. That is not a replacement for like traditional computer science in the sense of like algorithms. And if in fact a lot of those classes are prereqs to what I'm doing here.
4:59 But I do know that you have a good foundation, going now toward applying that and sort of using those principles in production environments in the real world, that's something that I think is now at a place where, you know, at Monarcha we deal with massive code bases. You know, I help a lot of companies also with thinking through their massive code base designs and things like that. And so it's more of a practitioner's course for once the students, graduated or now entering the workforce, how to be the most productive members workforce.
5:25 You said you're passionate about education. I feel like students in that phase of being in college are in a pretty interesting spot. any advice and any take should people study computer science right now?
5:40 Is Claude code and codex all we need? Like, I want to, you know, hear your thoughts. Yeah, I, you know, there's a lot of anxiety from students, as you can probably imagine. And I think a lot of what I'm trying to communicate this time around is that the anxiety, a lot of it still is here. And there was anxiety last year as well. But I want to make the case that a well -trained AI native engineer, and I know that's like a buzzy word, but let's say we'll dive into maybe what aspects that are most interesting.
6:10 A well -trained and native engineer can be some of the most useful assets to any company around.
6:17 This is the first week of class, actually. Week one, first lecture, I'm like, hey, I really believe that every company needs you, but the floor is much higher. You're entering as your first job out of school, but it's not sufficient to just be an L3, in a Google term, if you're going to use that kind of leveling system there. You have to generally be better than almost at the senior level going to this.
6:39 So like what can we, how do we get there more quickly? Right? And so I'm trying to say that there is still a core bit of like foundational software engineering that is important to have. Some of these core values of sort of how software systems are built and the trade -offs of those systems. then beyond that we go and, know, that's where I think you as the humans should still be valuable rather than, and the rest of the implementation details you can kind of defer more often.
7:02 Hmm. Yeah. This is something I've said before which is almost like the controversy it's like the kind of thing you say to be spicy but I almost I do genuinely kind of believe it which is most students are cooked some of them are going to be super valuable I don't think it's a very popular thing Stanford's kids are going to be fine right they're from Stanford but like what happens to like the rest of America right that is an over question it's a weird situation because I feel like a lot of education is slow to move like I'm even curious in how do you determine where do you put the end date to curriculum in a course on it?
7:39 You're teaching a Stanford modern software. That's changing everything. You cheat. You just get the people from the coding agents to come and speak, right?
7:48 Oh, yeah. Have them be the, yeah. That's a funny. New old guest lectures. Well, yeah. I mean, that was, okay. So on the guest lectures point, I think that was, I mean, that was also last year. That was also the case. So that was by design because I, look, I came in, right, and I'm saying, I'm a practitioner, as you pointed out, swyx. Like, I'm a practitioner. I do this thing on my, you know, my day -to -day.
8:09 I design these systems. You know, build these things in Monaco have seen that many times before. And so that being said, don't want to claim that I have all the answers today. And that would be, like, very, you know, a lot of hubris to make that claim. So the structure of the class was always here's one practitioner's sort of aggregated set of insights from working in the field, from talking to a lot of people in the field.
8:33 But then there's people that are like literally on the frontier, you know, seeing things even beyond that and invite them to sort of put their proposals forward, their view of the world forward. And that's why the guest lecture is there. I think it's really impactful for students to see big names, people actually doing it, like hear from them directly, be able to ask them. Of course, you know, they want to intern, they want to get jobs.
8:56 It's good to have guest lecturers. No, I think what he's saying. So, OK, I'll sort of rephrase. No. So, OK, there, you know, we've also interviewed Ange, who teaches the Coachella course. Right. Right. Which is like, here's all the names. It's only the names. Right. Whereas like he's actually also producing, you know, here's cloud code in 200 lines of code. Right?
9:15 Which is, no one's telling you to do that. No one's gonna come speak to you to do that. But like, yeah, when you wanna teach fundamentals and a framework that you can use and working understanding, this is the kind of thing you do. That's right, that's right, yeah, yeah, exactly. And I do think that there's a balance for this kind of material, to your point, is that there is a, you can't, it's not 100 % solidified.
9:34 I mean, by design, it's a feature and maybe a bug of some kind, but a big portion of the curriculum did change from last year, right?
9:42 And so there's like a dynamism to the whole development of the curriculum. But I'm trying to at least put forward that there are some things that I believe are kind of sticking around. And yes, prompting coding agents, they've gotten smarter. What does that mean in terms of the new ways of dealing with them?
9:53 But then still, Boris is also going to know something that I don't know, right? So let's have him also come to the table and share his learnings. One of the fun things I noticed this time around is a good bit of the portion is on open source contributions. What's the thinking behind that?
10:11 You have people… Yeah, yeah. This is one of the things that I’m honestly kind of most proud of and most excited about. I mean, this is about to be week two of the class. Yeah, so this is the very gracious open-source partners that I spent the greater part of this summer just kind of talking to
10:28 and getting them kind of excited about and interested in sort of this offering. Basically the idea was, so last year when I taught the class,
10:34 we had like nine assignments, and then we had like a capstone open-ended project, right? The nine assignments were basically me sort of like coming up with these pedagogical exercises. Like, oh, here’s a repo. Use an AI code review tool to, you know, post a code review, and then see: why is it good? Why is it not good? So, relatively pedagogical, honestly pretty easy. I think for a lot of folks, they could just like one-shot it, and I thought, okay, this is not that helpful. At this point, agents are around. I mean, they have—every student that I surveyed, you know, on Tuesday, not a single person really types by hand anymore. They’re like, everyone’s using coding agents. And this is, you know, like all sophomores, juniors at Stanford.
11:10 Do you survey them? What's the market share? Was that like what, what tools they use? Okay. I haven't yet, that's a good call. You should do it. Yeah. Yeah. I will do that. Spicy, Stanford prefers. No, no. Well, I think university, I think they'd have some, like most of the providers have like an educational program, right?
11:27 I mean, yeah, they're very generous on plans for students. Right, right. So I think by default, even before the class, there's like, you know, Claude license, I imagine cursor license. There's like probably a cognition license as well. don't know, you might know that better than I do. But I was able to also just accrue on top of that was, hey, like if I don't want people to be bottlenecked by the $20 a month subscription.
11:49 I want you guys to go, if you want to token max something just to see what's possible, then you should. And so, I'll come back to the partners, but the additional thing I was able to accrue through instead of talking to folks was additional credits for students. So like factory is also getting involved, the cognition folks are getting involved. OpenAI as well. But anyway, so for the open source partners, I sort of was like, okay, one of the things I'm most concerned about when it comes to educating of students is that if everyone is saying, kind of to Suix's point, like they're cooked, like what's going to happen to them?
12:19 There's almost like this sense of them being left behind. And I think that mentorship is a really important piece of just up -leveling everyone and making sure that there isn't this massive gap that occurs between the senior people that have already been in the industry before coding agents and know what's up and they adopt coding agents and they become amazing. And then the juniors that are just like, okay, now what do we do?
12:39 So in a sense, one of the kind of goals was, hey, coding agents are really good. I want to put you guys in situations where you're dealing with complex code bases, large code bases at scale. We're going to work with someone like what I think are among the best like AI native repos, you know, that all do AI focused things or either coding agents themselves or building tools in the service of agents, you know, in the modern world.
13:00 I want you guys to get involved with these projects. I want part of your assignments to be actually contributing to these projects. In the course of being in all those projects, you will actually be talking to the maintainers. They will be reviewing your code. They will be helping you build mental models of good software. In that way, there's effectively this passing on of the guard of true good software design in a way that I don't think most students get the opportunity to do.
13:20 And then there's the benefit, of course, that I'm sure some of them will get poached and picked up as part of doing well in those assignments. Yeah. One of the interesting things, for what it's worth, get a bunch of hate if I I don't say this. I think you say cooked versus cracked for dramatic effect. know, like, it's just nice to state extremes. Sure, sure. Yeah. So maybe we should go into the sort of detail of the curriculum.
13:46 Yeah. Is there anything else you want to explore at the top level? I mean, like, that's very helpful. Yeah. All that's there. Okay. I have high -level questions about students using tools, best practices. Are you pro it?
13:59 Like individual tutors. I'm assuming this will also be picked up by students. So, you know, before we dive straight into the course, just anything you have guidance on there for. Like in terms of what. You said you're passionate about education, right?
14:13 Like, yeah, there's also a stigma of side is how do teachers, professors use it? And then how can students best use these tools? That's not just throw your assignments in. It can kind of one shot it. How do you still learn if you have anything there?
14:28 Yeah, yeah. And I think that there's, still have some assignments thrown in there, which I think are not intended to be the hardest things in the world, but are meant to be more about concepts, like more conceptual things. Like, you know, what does a skill mean?
14:39 Sort of like maybe more of the tactical of some of these tools, skills, like agent code bases, like agents MDs, things like that. So there's a certain amount of just, hey, if you haven't heard these terms, kind of get up to speed on them. I do think most of the learning, though, in terms of the of putting the tools to the test will happen both in the OSS and then also final project where it's very open -ended.
15:00 And they'll have to just kind of explore something interesting. Cool. Yeah. So maybe, yeah, I just want to talk about, well, let's go through one, two, three, four, uh, to 10. Yeah. Uh, and then we'll dive in deeper. So like breath first, basically. Sure. Sure. Yeah. So we start with internals of coding agents. That's right. You teach people how to write their own Claude Code clone. It's very helpful that it's not open source.
15:23 And then? Yeah. Yeah. So, uh, week one, it's all, uh, internals of harnesses, you know, kind of build a coding agent from scratch. Uh, week two is more, okay, now assume that there's, how do we start thinking about like, context engineering at scale. So beyond just vanilla prompting. And then I think coupled with that is just, in doing that, thinking about tool design, MCP. People, I think for a while MCP was getting a lot of hate.
15:46 I'm still pro -MCP, I see it all the time. And so I think that there's, at this point, it's a standard that's existed and I think it will continue to exist. So talking about that, effective tool design, that's week two. Week three, I would say is more about just like skills and what does it mean to extend beyond simple purpose tools to more like procedures. And that's where we'll talk about skills.
16:06 And that kind of starts leading into the automation of agents. Week four is a lot of just of like the foundational pieces of how can you customize an agent. This is things like config files, a la AgentsMD, CloudMD, hooks, sub -agents. There's a lot of mechanisms that exist in modern harnesses which you can use for different purposes. So I want to expose students to that. Agent -ready code bases. This is probably one of my favorite topics.
16:33 It's like, and this is especially relevant for folks that are going into industry and thinking about at scale is, you know, essentially what does it mean to have a repo that's ready to be consumed effectively by an agent?
16:45 And so thinking a lot about, you know, the trade -offs of designing of of service level boundaries, but also docs and verifiability and things of that nature. So that's week five. Yeah, week six, sort of agentic code review. And here I think what is interesting is thinking also kind of extending from week five, week five around code base, like agent -ready code bases. Going to week six is more about like, okay, in order to, like code review is now becoming a bottleneck, which I don't know that students, unless they've, you know, have done a lot of, some of them are master students, so they've been in the industry, but a lot of them have not seen this.
17:17 But for most people that are using code agents today, we're all experiencing something of a new bottleneck in code review. So how do we unblock that or sort of unbottle the bottleneck a little bit?
17:27 What mechanisms are there there? And so verifiability and things of that nature and how we can extend that into the code review process. Week seven, security. I mean, obviously, I think there was a point. So this was in last year's class as well, and this I wanted to reinforce. I mean, with any autonomous system taking a lot of actions, we're seeing a lot of this year, especially a lot of things getting hacked.
17:48 You know, not least of which are just some of the core pieces of software from Vercel to, know, gateways, LM gateways entirely. So I want to spend some time just like talking about what new attack vectors exist in security and, you know, how we can mitigate some of them. Week eight is background agents. So this is what I want to start touching on here is, you know, how do you like basically run agents in many different product service areas, not just in what was traditionally an IDE, but also having things that are based on triggers in your code base and in your repo during CICD, things that get triggered even when based on events, things like SRE style bots.
18:31 How do you even build a system like, I think this past year was when a lot of companies started releasing their posts like ramp inspect. Spotify has their own version of this, I think Stripe Minions, so all these folks were doing really cool write -ups of their internal infra they were building to do this. I want to touch on that, get people exposed to what that is. Yeah, this one is more on what happens when you're in a team the modern world and sort of like the core pieces of team -level infrastructure.
19:00 So everything from LM Gateways to MCP Portals, which is like MCP at scale, and then just also how to think about the evolving roles, I would say. So this is maybe a little bit like a soft thing. It's like what is now, you know, and the vanilla, maybe like not super nuanced thing to say is like everyone's a builder, but I want to go a little bit deeper beyond that and like sort of like what thing is actually getting subsumed?
19:22 What roles are actually either evolving or emerging that didn't once exist? What should students think about in terms of defensible skill set that's maybe wasn't true before?
19:31 And so a lot more like team dynamic type considerations. And then, yeah, this is it all kind of builds up toward the factory, which I think is top of mind for now. for a lot of folks today. Once we're building factories, do humans still exist and all that?
19:46 What are the new choke points that are intentionally there around human involvement? Things like intent, things like setting up a verifiable systems. And what happens in the limit when maybe 80, 90 % of code is fully driven by just agents, where we kind of filled into all that. So, yeah. Nice, solid 10 weeks. I was gonna say, like, know, some of these are more established patterns than others. And, I think people need to know that, like, not all of this is settled science.
20:18 Sure. But it is everything, I'll endorse everything as things that people talk about and you should know. We know the open problems, we may not know the answers. That's absolutely right. Yeah. I mean, you probably have your own version of this. I'd be curious to hear what you think is still not as defensible, or not defensible, but not as set in stone. But even like the software factory, are we talking about dark factories?
20:39 Are we talking about these sort of half lights on factories? I think even there's a spectrum there. Yeah, and there, you know, the people that are on the very frontier, like the warps and the factories that are like building factories and selling them services. And, you know, even they only claim like 30 some percent of even that of like fully, you know, agentically driven So, what does that mean in the limit?
21:00 It is hard to say. And there's people who went very, very far dark factory and then came out saying I was wrong, guys. Yeah. Right. So, like, we covered that on AIE. just be aware that not everyone, they probably believe the things they're saying at the time but they have the right to change their mind and they do and even Boris recently tweeted that yeah I am often wrong and everyone is like, because he created Clock Code, it's like treating his word as gospel and I'm like no, sometimes he disagrees with himself and that's okay this isn't politics, right we're still scientists, we're engineers we're subject to, I don't I don't claim to be dogmatic, but I just want people to experiment.
21:40 I think that's a principle as well. You asked about principles earlier. Just experimentation. I mean, you just have to be ready to ... And oftentimes, when I give these lectures or talk to people about this stuff, they're like, there's so much going on. How do I stay on top of this?
21:52 There's something as simple as just experimenting for 10 minutes a day. Just spending 10 minutes doing something that you didn't do before. If that's a traditional way that you were solving a problem, there's now a new tool that you want to try or a new framework or something. And just spending, maybe even doing the exact same problem just with that new kind of thing alone will cover most of the gap. Yeah.
22:10 I will call out, so some of your, for example, you have Cognition on the week that you're talking about Code Review. Yeah. I actually did work with Silas on Devon Review. Yeah, yeah. Pretty good, I would say. hard to benchmark these things. There is a ReviewBench. No one uses it. But qualitatively, Devon Review is pretty good. Well, we use you guys. Oh, really?
22:30 Yeah, so Monaco does use Devon. And Silas actually spoke last year, and so Silas is great. It's just super, super smart. But yeah, we use you guys. And so I was like, okay, among the providers of kind of code review tools that we, and we sampled a lot of them. We actually did kind of converge on Devon for a lot of use cases. Silas is actually of a model side these days, and then actually Walden that you want.
22:51 Yeah, yeah, yeah. I spoke to Walden as well. I will also shout out, you know, from Factory, because, you know, talking about agent readiness, They've been all about that. They build signals, tooling on that. Do you guys use that?
23:02 Yeah, yes. So we do use agent readiness of our own kind. I mean, Eno is awesome as well. I think they were super early on this train. think when he codified that in his talk, I guess, at AIE, what was it, like last, I forget when it was, but one of his talks. Europe, yeah. Yeah, Europe, just fantastic talk. And I think it was kind of way ahead of its time. And so I was like, there's only one person that I could see being the most appropriate person to talk about this where I really want to give them the spotlight and super excited.
23:27 Yeah, it was funny. I was at Cog. We were talking about this stuff and we were like, okay, we need to form some opinions about it. And then like Factory like shipped a full product on it that week that we were talking about it. I was like, okay, you won. I mean, like everyone kind of agrees on the same thing. And it's just a question of like, do you want to turn it into a dashboard?
23:45 Because it's a dashboard. Right, right, right, right, right, right. But you know, there's value. And like, I think they did well from a marketing perspective jumping on the writings and report. And I've definitely spoken to, you know, I will regularly kind of pitch that to other people and say, like, yeah, you should run writings and reports of your own kind. And, you know, of course people have open source versions of it, but I think the principles are super important.
24:04 Yeah. Do you want to go piece by piece or do you have any other things? I can go piece by piece. Yeah, okay. So the first one, right?
24:11 You focus on cloud code, but then you also have Pi as an open source sponsor. What's up? Okay, so this one is maybe a little bit more marketing -y, but okay. The one thing I do want to highlight, and I've made that, I also made that clear last year, but I'm not endorsing any tool, okay?
24:26 Like, I don't, I think that is the wrong way to approach something like this. There are tools that come and go, and you know, transparently, when the class was taught last year, Cloud Code was not as popular. It wasn't as, like, really accepted. Boris was only at 4 ,000 Twitter followers, and now he's at, you know, whatever million. I don't even know if he is. He's had a lot of followers. Cloud Code has really, like, emerged on the scene.
24:49 I think what. Yeah, I think we, we also underestimated Claude Code when we had Boris and Kat on the podcast. Right, right. It was, like, two months old. I hadn't really, like, I used it once. A query cost me 50 cents. I was like, who's going to use this shit?
25:00 Totally. It was still in beta for a while. But I think it's good on them for how they built it before the model was ready. Yes. Like, you hear so much build for where the model will go. Totally. Super ambitious. Like, models were not that good. You couldn't feel it. And then, ah, we see, we see that. That's where it came from. Yeah, it's funny, because when he gave his talk last year, I remember, it was like a very high level of set of slides, but I remember one of the slides was literally built for where the model's gonna be six months from now.
25:23 And this was like October of last year, and I can see why he would've made that point if he knew in six months where Opus was gonna be, because that was also what I think was a huge unlock, where I would argue is one of the reasons why the curriculum changed as much as it did, right?
25:37 Where there was certainly this huge arms race around true autonomy in these agents, like long -running agentic agent tasks. But yeah, so back to your point, it's like less on, I'm not endorsing Cloud Code. I mean, Cloud Code, of course I use it and use other things as well, but here I was more about like the, what does a modern coding harness look like?
25:54 I wrote a blog post actually, yeah, this one, this was earlier this year, where I sort of broke down some similar -ish principles The TLDR was that you could sort of, through like pretty much introductory algorithms level understanding, could just find like essentially an agentic loop that does the bulk of what you would call a coding agent. And of course there's like bells and whistles, there's no sub agents, there's an MCP and none of that stuff.
26:18 But if you want to see something that you talk to and then it literally will edit your file and you can do pretty sophisticated things with it, it doesn't require more than 200 lines. So a lot of what I try to do in education is to try to peel away the stuff that's like the secret sauce show that really at its core, I mean, these are still students and you want to teach conceptual principles.
26:37 There's nothing more to this than, in Stanford, there's this class called 106B. It's like the introductory algorithms. You don't need more than 106B to build something like this. So you go. There it is. Given that you already taught this class, pushback, any questions, any weirdness that you observe from the students?
26:54 What do they not get? What do they seem to cluster questions around? You mean like now that this particular concept or just in general?
27:02 This concept. Of like building it from scratch and then doing what you did. Because this is basically what you needed for Pi. Right, right, right. Exactly right, yeah, yeah, yeah. So it's not really. I think they're, I haven't received any pushback on this idea at all. I think they're actually more just, most of them are consumers, right?
27:21 Most of the students do just end up using the tools. I don't think that they get a lot of exposure, if any, certainly in the coursework, around peeling that onion back. And I think, so this was the week of the harness. So Tuesday, first lecture, logistics, blah, blah, blah, all that stuff. But then first half is, the first true bit of curriculum is the 200 lines of a harness. And then yesterday, when I had sort of the follow -up to that, is we actually took Cloud Code, and then you have these proxy things, You need like for proxy tools where you can intercept the request.
27:53 MIT and proxy? Yes, exactly. Exactly right. So use that. Use that tool. Intercept the requests and responses. Nice. Look under the hood, see what's happening there. And then just like, OK, I did say you have Claude code in 200 lines. But really, OK, here's like actual Claude code. And so what I literally did is I took Opus 5.5, so this model of two days old, and was like, this is, I intercepted those requests.
28:13 Here's exactly what's going on. Here's the prompt. Here's the system prompt. Here's the plan prompt. Here's the compaction prompt. And then we just went through all of that and sort of showed it to the students. So now they really, really have like a state of the art harness that they can understand. Yeah. It's nice to get those three levels. Like students are very much consumers. Here's the baseline agent in a loop and then the real one.
28:32 I like how you have a video walkthrough of your blog post as well. Do you see s
正文以来源语言显示。