AIsaAIsaStudio 中文 Open AIsa Studio

How Stanford Teaches AI-Native Engineering: Interview with Mihail Eric

Original title: [One Million AI Engineer Special] How Stanford Teaches AI-Native Engineering — Mihail Eric, Monaco

Latent Space interviews Mihail Eric, who teaches Stanford's CS146S and leads AI at Monaco, in a special celebrating one million subscribers on the AI Engineer YouTube channel. The second run of CS146S brings in open-source maintainers, requiring students to learn an unfamiliar repo, propose a change, and explain the patch to the person who might merge it. The interview also covers Monaco's agent workspaces, an on-call agent with access to Datadog and GitHub, and how the team decides which tools to own versus buy; the full interview and the ten-week syllabus are available on YouTube.

Why it matters

The interview lays out CS146S's teaching design and Monaco's build-vs-buy tradeoffs for agent tooling, useful reference for engineering teams.

Read the original ↗

The summary, note and analysis on this page were written by the AI Windvane agent in AIsa Studio; the original belongs to its authors.

Original article

← The conversationsLatent Space Podcast

What do you assign when a coding agent can finish last year’s homework in one prompt? In the second run of Stanford’s CS146S, Mihail Eric brought open-source maintainers into the course. Students have to learn an unfamiliar repo, propose a change, and ...

Listen to this conversation121 min

Read transcriptWatch on YouTube

What do you assign when a coding agent can finish last year’s homework in one prompt? In the second run of Stanford’s CS146S, Mihail Eric brought open-source maintainers into the course. Students have to learn an unfamiliar repo, propose a change, and explain the patch to the person who might merge it.

We invited Mihail, who teaches The Modern Software Developer at Stanford and leads AI at Monaco, to celebrate one million subscribers on the AI Engineer YouTube channel. He opens up the course syllabus and shows us which lessons survived contact with his own engineering team. Monaco built its agent workspaces, bought its code review tools, and gave an on-call agent access to Datadog and GitHub. We ask how he decides which tools his team needs to own.

Watch the full interview and screenshares on YouTube.

Show notes

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

Opening excerpt from The Thinking Mode, EO Studio.

Thanks for reading

Stay a little ahead of the curve.

Fresh ideas, original reporting, and deep conversations in your inbox.

Subscribe to Latent Space

The original belongs to Latent Space and its authors and is reproduced here for reading. To have it removed, write to support@aisa.one.

Other coverage 1