← Lenny's Podcast: Product | Career | Growth

Head of Claude Code: What happens after coding is solved | Boris Cherny

第2026-02-19期2026-02-19English会员内容

嘉宾:Boris Cherny

Head of Claude Code: What happens after coding is solved | Boris Cherny
收听本集00:00 / 1:27:45
阅读设置
按你的习惯阅读
正文字号
下载播客精读
把这一篇,带走慢慢读

英文 · 精读 · 当前版本

下载功能还未开放

正文语言

精读 · 按主题梳理核心观点、论证与案例。

§01When coding becomes abundant

Boris Cherny describes a software workflow in which Claude Code writes all of his code, while he ships 10–30 pull requests a day and runs several agents in parallel. He says coding is more enjoyable because he no longer handles minutiae, and estimates that productivity per engineer has increased 200%. He expects coding to be nearly solved within a year or two, making software construction available to anyone rather than only trained engineers.

The next change is not simply faster code generation. Claude is beginning to identify ideas by reading feedback, bug reports, and telemetry, then proposing fixes and things to ship. Cherny predicts that everyone may become a product manager and builder as software-engineer boundaries blur. The episode introduces his work at Anthropic, the rapid growth of Claude Code, and the safety mission that drew him back after a short move to Cursor.

§02From coding tool to general agent

Claude Code’s growth reflects a broader shift from code generation to agentic work. Cherny describes a trajectory from coding, to tool use, to computer use, with safety as a central reason for developing capabilities in stages. Cowork extends that transition to nontechnical users by allowing an agent to act through tools such as Gmail and Slack. The team explored model boundaries through prototypes, research, and a deliberately minimal terminal interface rather than a heavy predesigned environment.

好对话,值得读完整。

免费试读到此结束。开通书架会员,继续阅读全文,解锁中英对照与电子书下载。