←News detail

Shao MengUpdated Oct 25 23:46

Claude Code creator Boris Cherny shares five practical Agent principles in a Stanford class

English text is being prepared.

AI summary

Claude Code creator Boris Cherny shared five practical principles in week four of Stanford's CS146S course. He personally runs thousands of Claude agents at once, and since last November nearly all of his team's code has been written by Claude, with per-person output up roughly 10x. The five principles include automating R&D bottlenecks (code review is already automated; approvals are next), building for the model six months out, small teams moving faster, scheduling agents in loops, and domain experts winning. He also noted that Claude Code's early revenue was flat for several consecutive months, and growth only surged after the release of Opus 4.

Why read this

AI score 67

The Claude Code creator's approach of automating R&D bottlenecks and designing ahead for future model capabilities offers a transferable engineering playbook for teams.

Topics

Tags

Quoted post

Mihail Eric

@mihail_eric

I asked @bcherny how many Claude agents he's running right now as he sat next to me. "A few thousand." Boris (creator of Claude Code) came back to my Stanford course The Modern Software Developer last Thursday. His main takeaways: - Automate your bottleneck: Claude has written 100% of his team's code since November and output is up ~10x per engineer. So much code shipped that people stopped reading it carefully and started skimming, so they automated code review. Approvals are next. The team identified the main things impeding their development velocity and built systems to unblock themselves. - Build for the model 6 months out: early Claude Code revenue was flat for months because the model wasn't smart enough yet. Then Opus 4 came out and growth became astronomic. His method is to read your agent transcripts and see where the model fails. That's where it will improve in the next model release. - Small teams go faster: for months Claude Code was basically just him. With AI, one or two people can outship a team 100 times their size. Constraints breed creativity. - Think in loops: his grandpa programmed punch cards in the Soviet Union. Boris writes loops that run for days or weeks and spawn many agents. He expects that typing code by hand is heading where punch cards went. - Domain-specific builders are the future: he expects the best accounting software of 2027 to be built by an accountant. When code is cheap, knowing the problem deeply is the only alpha In the 50 years after the printing press, Europe produced more literature than in the previous 1,000. He thinks coding is about to undergo a similar explosion of creation.

View original

I asked @bcherny how many Claude agents he's running right now as he sat next to me. "A few thousand." Boris (creator of Claude Code) came back to my Stanford course 𝗧𝗵𝗲 𝗠𝗼𝗱𝗲𝗿𝗻 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 last Thursday. His main takeaways: - 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝘆𝗼𝘂𝗿 𝗯𝗼𝘁𝘁𝗹𝗲𝗻𝗲𝗰𝗸: Claude has written 100% of his team's code since November and output is up ~10x per engineer. So much code shipped that people stopped reading it carefully and started skimming, so they automated code review. Approvals are next. The team identified the main things impeding their development velocity and built systems to unblock themselves. - 𝗕𝘂𝗶𝗹𝗱 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹 𝟲 𝗺𝗼𝗻𝘁𝗵𝘀 𝗼𝘂𝘁: early Claude Code revenue was flat for months because the model wasn't smart enough yet. Then Opus 4 came out and growth became astronomic. His method is to read your agent transcripts and see where the model fails. That's where it will improve in the next model release. - 𝗦𝗺𝗮𝗹𝗹 𝘁𝗲𝗮𝗺𝘀 𝗴𝗼 𝗳𝗮𝘀𝘁𝗲𝗿: for months Claude Code was basically just him. With AI, one or two people can outship a team 100 times their size. Constraints breed creativity. - 𝗧𝗵𝗶𝗻𝗸 𝗶𝗻 𝗹𝗼𝗼𝗽𝘀: his grandpa programmed punch cards in the Soviet Union. Boris writes loops that run for days or weeks and spawn many agents. He expects that typing code by hand is heading where punch cards went. - 𝗗𝗼𝗺𝗮𝗶𝗻-𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗯𝘂𝗶𝗹𝗱𝗲𝗿𝘀 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗳𝘂𝘁𝘂𝗿𝗲: he expects the best accounting software of 2027 to be built by an accountant. When code is cheap, knowing the problem deeply is the only alpha In the 50 years after the printing press, Europe produced more literature than in the previous 1,000. He thinks coding is about to undergo a similar explosion of creation.

View original post

Body

@stanfordnlp 教授 @mihail_eric 教授秋季新课「CS146S: The Modern Software Developer」,课程介绍: https://t.co/AhFJW6xl8V

课程第四周,请到了 Claude Code 作者,Boris 分享的核心并不是“多用 AI 写代码”,是把研发瓶颈系统化地自动化掉,并为六个月后更强的模型提前设计。他自己身边同时跑着“几千个” Claude agent;团队从去年 11 月起代码已接近全部由 Claude 写出,人均产出约提升 10 倍。 https://t.co/9iItZYGIze

# 五条要点

1. 自动化你的瓶颈 代码写得太多以后,人开始只扫一眼、不再细读,于是他们把 code review 自动化了;下一步是审批。做法是先找出拖慢交付的环节,再为这些环节建系统,而不是泛泛“全面 AI 化”。

2. 为六个月后的模型而建 Claude Code 早期收入曾连续数月几乎持平,因为当时模型不够强;Opus 4 出来后增长才陡升。他的方法:读 agent 对话记录,看模型现在会在哪里失败;那里往往就是下一版模型会补上的能力。

3. 小团队更快 Claude Code 有好几个月基本就是他一个人。他认为有了 AI,一两个人可以超过百倍规模的团队;约束反而催生创造力。

4. 用“循环”思考 他祖父在苏联用穿孔卡片编程;他自己写能跑几天甚至几周、并不断拉起大量 agent 的循环。他预期手敲代码会逐渐变成穿孔卡片那样的过时技能。

5. 懂领域的人会赢 他预计 2027 年最好的会计软件会由会计来做。当写代码变便宜,真正的壁垒是对问题本身的深度理解。

Source

Shao Meng