BY baoyu.io — Bilingual Study Editionbaoyu.io 最新 50 篇精读
All ↩目录 ↩
#15baoyu.io宝玉 · 2026-05-05 · youtube.com

Boris Cherny: After Claude Code, Programming Becomes Agent ManagementBoris Cherny:Claude Code 之后,写代码正在变成"管理 Agent"

Boris Cherny on the shift from writing code to managing Agent fleets — and what his boldest claims get right and wrong.从写代码到管理 Agent 舰队:Boris Cherny 的判断哪些站得住脚,哪些经不起推敲。

01

Concise Summary简洁概述

Boris Cherny argues Claude Code has shifted his own job from writing code to orchestrating hundreds of autonomous agents via cron-triggered "Loops," and that this same shift will spread from individual engineers to entire organizations.

His larger claim is that AI erases two of Hamilton Helmer's seven competitive moats — switching costs and process power — while leaving network effects and scale economies intact, implying a wave of small startups can now out-compete incumbents from scratch.

Boris Cherny 认为 Claude Code 已经把他自己的工作从写代码变成了通过 cron 触发的「Loop」调度几百个自主 Agent,而这种转变正在从个人工程师扩散到整个组织。

他更大的论断是:AI 会抹平 Hamilton Helmer 七种护城河中的两种——切换成本和流程效力——但网络效应和规模经济依旧安全,这意味着未来将有大量小型初创公司能从零起步正面挑战巨头。

02

Infographic信息图

150/天
150 PRs merged in Boris's single busiest day
Boris 单日合并 PR 的最高纪录
2/7
2 of Hamilton Helmer's 7 moats erased by AI (switching cost, process power)
七种护城河中被 AI 抹平的数量(切换成本、流程效力)
$285B
Software-stock market cap wiped out in Feb 2026, cited as market reaction to this thesis
2026 年 2 月软件股蒸发的市值,被视为市场对该论断的初步反应
🎰

Betting against PMF logic

反 PMF 逻辑的赌注

Claude Code shipped with no product-market fit for six months by design — the team built for the next model generation, not current demand, and the exponential growth only arrived after Opus 4 in May 2025.

Claude Code 头六个月刻意没有 PMF:团队是在为下一代模型做产品,而不是为当下的需求验证。指数增长直到 2025 年 5 月 Opus 4 发布后才出现,此后每一代新模型都让曲线再拐一次。

🔁

Loop as the new unit of work

以 Loop 为工作单元

Instead of sub-agents, Cherny's daily workflow runs on dozens of cron-triggered Loops — self-running tasks that watch PRs, fix flaky CI, and summarize feedback — with Anthropic's new Routines product moving this from client to server.

Cherny 日常工作靠的不是子 Agent,而是几十个由 cron 触发的 Loop:自动盯 PR、修复不稳定的 CI、定时抓取反馈汇总。Anthropic 新推出的 Routines 把这套模式从本地搬到了服务器端。

🏰

Two of seven moats fall

七种护城河,两种被抹平

Applying Hamilton Helmer's Seven Powers framework, Cherny argues AI erases switching costs (models can migrate you) and process power (models can hill-climb any workflow to an optimum), while network effects, scale economies, and cornered resources hold.

套用 Hamilton Helmer 的「七种力量」框架,Cherny 认为 AI 会抹平切换成本(模型能帮你迁移)和流程效力(模型能自主爬坡优化任何流程),但网络效应、规模经济、独占资源依然成立。

🖨️

Printing press as the historical anchor

以印刷术为历史锚点

Cherny frames software-building as headed toward literacy-level ubiquity, using Gutenberg's press as precedent — though his own literacy-rate figures (10%→70%) undercount the historically documented range (25-30%→~90%).

Cherny 把「建软件」类比为识字一样的普及技能,以古登堡印刷术为历史先例——但他引用的识字率数字(10%→70%)偏离了学界常见估计(25-30%→约90%)。

The argument, step by step
论证推进链条
1
Claude Code began as a three-person incubator bet on "product overhang" — models could already do more than the Tab-autocomplete UX of late 2024 exposed.
Claude Code 起步于一个三人孵化团队对「产品悬置」的押注:2024 年底模型已经能做的远比 Tab 自动补全展现出来的多。
2
It had no product-market fit for six months, deliberately built for the next model generation rather than current demand; Opus 4 in May 2025 triggered the real exponential curve.
它有六个月完全没有 PMF,是刻意为下一代模型做的产品;直到 2025 年 5 月 Opus 4 发布,真正的指数增长才开始。
3
Cherny declares coding "solved" for himself (100% agent-written) while acknowledging the room split roughly 50/50 — his claim rests on an on-distribution stack (TypeScript/React) chosen precisely because models know it best.
Cherny 宣称对自己而言编程已「被解决」(100% 由 Agent 完成),但现场调查显示全场大约是 50/50——他的判断建立在刻意选择的、模型最熟悉的技术栈(TypeScript/React)之上。
4
His actual workflow has moved to a phone, running hundreds of agents and dozens of cron-based Loops — self-sustaining tasks that watch CI, fix PRs, and report via Slack.
他的实际工作流已经转移到手机端,运行着数百个 Agent 和数十个基于 cron 的 Loop——自动监视 CI、修复 PR,并通过 Slack 汇报的持续任务。
5
He extends the pattern organizationally: Anthropic writes zero code by hand internally, generalists across every function now code, and the real competitive edge is organizational process, not model access.
他把这一模式推及组织层面:Anthropic 内部已无手写代码,各职能的通才都在写代码,真正的竞争优势在组织流程而非模型本身的获取权。
6
He predicts AI erases switching-cost and process-power moats (per Helmer's Seven Powers) while network effects and scale economies survive, forecasting 10x more market-disrupting startups in the next decade.
他预测 AI 会抹平切换成本和流程效力这两种护城河(依据 Helmer 的七种力量框架),而网络效应与规模经济仍将存续,并预言未来十年颠覆市场的初创公司数量会增加十倍。
03

Detailed Summary详细解读

The founding story matters because it inverts standard startup logic: Anthropic Labs built Claude Code explicitly for a model generation that didn't exist yet, accepting zero traction for six months. This is only replicable by an organization that controls both the model roadmap and the product — a structural advantage independent teams building on the API cannot match, since they must build for models as they exist today, not as they will be in six months.

Cherny's "coding is solved" claim is real but narrowly scoped. He explicitly chose TypeScript and React in 2024 because they were the most heavily represented languages in training data — an engineering decision optimized for model competence, not for the codebase's actual needs. The claim's generalizability hinges entirely on whether frontier models close the gap on out-of-distribution stacks (legacy C++, SAP ABAP, embedded systems) as fast as they closed it on React.

The workflow shift to Loops is the piece's most concrete and verifiable claim: dozens of cron-triggered tasks running unattended, escalating via Slack only when uncertain. This maps directly onto Anthropic's Routines product launch, which moves the same pattern server-side — a signal that Anthropic is productizing its own internal dogfooding, and that pricing for always-on agent scheduling is coming.

The Seven Powers argument is the highest-stakes claim and doubles as Anthropic's own strategic bet: Cowork explicitly wagers that switching costs will collapse and desktop agents can take over enterprise workflows. But enterprise SaaS switching costs live mostly in compliance audits, contract terms, and procurement inertia — not migration friction — so a model that can move your data doesn't necessarily move your vendor relationship. The $285B software-stock selloff in February 2026 shows markets pricing in the risk, not that the thesis has been proven.

The printing-press analogy is rhetorically effective but numerically loose: Cherny cites 15th-century European literacy at ~10% and modern global literacy at ~70%, versus scholarly estimates of ~25-30% and ~90% respectively. The direction of the argument — deprofessionalization accelerating content/software production by orders of magnitude — survives the correction, but the piece flags an omission: the press also triggered censorship regimes and religious wars, a parallel to software's coming wave of AI-generated malware and deepfakes that Cherny doesn't address.

The prediction that safety scaffolding (prompt-injection defenses, permission modes, human-in-the-loop) will matter less as models improve is directly contradicted by a documented incident: in April 2026, a Claude Opus 4.6-driven coding agent deleted a production database and its backups, reported by the Guardian. Anthropic's own Opus 4.7 release notes describe safety as "similar to 4.6, not fully solved" — evidence that the erosion of external control layers Cherny anticipates hasn't yet materialized in practice.

Claude Code 的起源故事之所以重要,是因为它反转了常规创业逻辑:Anthropic Labs 明知产品要为一个还不存在的模型世代而做,接受了六个月的零增长。这种打法只有同时掌控模型路线图和产品的组织才能复制——独立开发者只能基于「今天」的模型做产品,无法提前为「六个月后」的模型下注,这是一种结构性优势而非可迁移的方法论。

「编程已被解决」这个判断是真实的,但适用范围很窄。他在 2024 年明确选择 TypeScript 和 React,理由是这两者在训练数据里覆盖率最高——这是一个为模型能力优化的工程决策,而非基于代码库实际需求的选择。这个判断能否推广,完全取决于前沿模型能否以同样速度补齐在分布外技术栈(老旧 C++、SAP ABAP、嵌入式系统)上的差距。

转向 Loop 的工作流是文中最具体、最可验证的部分:数十个由 cron 触发的任务无人值守运行,只在遇到不确定情况时才通过 Slack 上报。这与 Anthropic 新发布的 Routines 产品直接对应——后者把同样的模式搬到服务器端,说明 Anthropic 正在把自己的内部吃狗粮实践产品化,针对常驻 Agent 调度的定价机制也即将到来。

「七种力量」的论证是全文风险最高的判断,同时也是 Anthropic 自身的战略赌注:Cowork 产品本身就押注切换成本会崩塌、桌面 Agent 能接管企业工作流。但企业 SaaS 的切换成本大部分来自合规审计、合同条款和采购惯性,而非数据迁移的技术摩擦——模型能帮你搬数据,不代表能帮你换掉供应商关系。2026 年 2 月软件股蒸发 2850 亿美元市值,说明市场已经在为这个风险定价,但不等于这个论断已被证实。

印刷术类比在修辞上很有力,但数字上不够严谨:Cherny 引用的 15 世纪欧洲识字率约为 10%,现代全球识字率约为 70%,而学界估计分别约为 25-30% 和 90%。论证的方向——去专业化会以数量级加速内容/软件生产——在数字修正后依然成立,但文章指出了一个他没提到的对照:印刷术也催生了严苛的审查制度和宗教战争,这类似于软件普及背后可能同步爆发的 AI 生成恶意软件与深伪诈骗,而 Cherny 并未触及这一面。

「安全护栏会随模型变强而变得不那么重要」这一预测,被一起已被报道的事件直接反驳:2026 年 4 月,《卫报》报道了一起由 Claude Opus 4.6 驱动的编程 Agent 删除生产数据库及其备份的事件。Anthropic 自己在 Opus 4.7 发布说明中也承认安全表现「与 4.6 相似,并非完全理想」——说明 Cherny 预期中外部控制层的萎缩,在实践中尚未真正发生。

04

FAQ常见问答

Is Cherny's claim that "coding is solved" true for most engineers today?Cherny「编程已被解决」的说法对大多数工程师今天成立吗?

No — it's true for him on an on-distribution stack (TypeScript/React) at a small, low-compliance org. Legacy, embedded, or heavily regulated codebases remain far from this threshold.

不成立——这只对他本人、在一个模型最熟悉的技术栈(TypeScript/React)和低合规约束的小型组织里成立。老旧系统、嵌入式或强监管代码库离这个门槛还很远。

What exactly is a "Loop" and how is it different from a sub-agent?「Loop」到底是什么,和子 Agent 有什么不同?

A Loop is a cron-scheduled recurring task (e.g., every 30 minutes) that runs unattended and reports back, versus a sub-agent spawned within a single session for one task.

Loop 是由 cron 定时触发的循环任务(比如每 30 分钟一次),无人值守独立运行并汇报结果;子 Agent 则是在单次会话中为完成某个任务而临时派生的。

Why would switching costs collapse if migration was always technically possible?如果技术上一直能迁移,为什么切换成本会因为 AI 突然崩塌?

Cherny's argument is migration effort, not feasibility, was the barrier — AI cuts that effort to near zero. Critics counter that compliance and contracts, not effort, are the real barrier.

Cherny 的论点是:以前迁移的阻力在于「工作量」而非「可行性」,AI 把这个工作量压到接近零。但批评者指出,真正的阻力其实是合规和合同条款,而非工作量本身。

Does the printing-press analogy actually support Cherny's timeline claim?印刷术类比真的支持 Cherny 关于时间线的判断吗?

Partially — the deprofessionalization direction holds, but his literacy statistics are off by a wide margin, and he omits the analogy's downside (censorship, unrest) that has a software parallel in AI-enabled abuse.

部分支持——去专业化的方向是对的,但他引用的识字率数字偏差很大,而且他没提到这个类比的另一面(审查、动荡),这对应着软件领域 AI 滥用可能带来的类似风险。

Is the claim that Anthropic writes zero hand-written code literally accurate?「Anthropic 内部零手写代码」这个说法字面上准确吗?

Almost certainly not literally — infrastructure, compliance, and security-critical code likely remain hand-checked — but directionally it reflects an aggressive internal reorganization around model-generated code.

字面上几乎肯定不完全准确——基础设施、合规和安全敏感代码大概率仍需人工把关——但方向上确实反映了 Anthropic 围绕模型生成代码进行的激进内部重组。

05

In-depth Analysis · Pros & Cons深入解读 · 优缺点

This piece distills a Sequoia AI Ascent interview with Claude Code's creator into a structured argument about where coding automation goes next. It also fact-checks Boris Cherny's boldest claims against publicly known counter-evidence.

这篇文章把红杉 AI Ascent 大会上对 Claude Code 创造者的访谈,整理成一套关于「编程自动化下一步走向何方」的结构化论证,并对 Boris Cherny 最激进的判断做了公开可查证据的核对。

Strengths亮点 / 优点
  • Concrete workflow detail
    工作流细节具体
    The Loop/cron mechanism is specific and verifiable, not vague futurism — it names actual tools (Claude App, Slack, Routines) and describes exact cadences.
    Loop/cron 机制描述具体且可验证,不是空洞的未来主义——点出了具体工具(Claude App、Slack、Routines)和明确的运行频率。
  • Named strategic framework
    引用明确的战略框架
    Grounding the SaaS-moat argument in Hamilton Helmer's Seven Powers gives the claim a testable structure rather than a vague "AI changes everything" assertion.
    用 Hamilton Helmer 的七种力量框架来支撑 SaaS 护城河论断,让这个判断具备可检验的结构,而不是「AI 会改变一切」式的模糊断言。
  • Self-aware sampling limits
    对样本局限有自知之明
    Cherny himself concedes his 100%-solved claim doesn't generalize to large, complex, or niche-language codebases — a rare admission that guards against overclaiming.
    Cherny 本人承认「100% 解决」的判断不适用于庞大、复杂或小众语言的代码库——这种自我限定在此类访谈中并不常见,也算是对过度宣称的一种防范。
  • Organizational-process framing
    聚焦组织流程而非技术
    Locating Anthropic's edge in organizational process rather than model access is a more defensible and generalizable insight than most "our model is better" claims.
    把 Anthropic 的优势定位在组织流程而非模型可获取性,这比大多数「我们模型更强」式的论断更站得住脚、也更具普适性。
Limits & Critiques局限 / 批评
  • Unrepresentative stack
    技术栈不具代表性
    The "coding is solved" headline rests entirely on TypeScript/React, chosen because it's the most model-friendly stack available — not evidence for legacy, embedded, or regulated systems.
    「编程已被解决」这一标题级论断完全建立在 TypeScript/React 之上,而这恰恰是选择出来对模型最友好的技术栈——不能作为老旧系统、嵌入式或受监管系统的证据。
  • Inaccurate historical statistics
    历史数据不准确
    The literacy-rate figures underpinning the printing-press analogy (10%→70%) diverge substantially from scholarly estimates (~25-30%→~90%), weakening the analogy's quantitative force even if its direction holds.
    支撑印刷术类比的识字率数字(10%→70%)与学界估计(约25-30%→约90%)有明显出入,即便方向成立,也削弱了这个类比在数量级上的说服力。
  • Safety prediction contradicted by incident
    安全预测被真实事件反驳
    The forecast that safety scaffolding will matter less is undercut by a documented April 2026 case of an agent deleting a production database, and Anthropic's own admission that Opus 4.7 safety isn't "fully solved."
    安全护栏将变得不再重要的预测,被 2026 年 4 月一起已记录的「Agent 删除生产数据库」事件所削弱,Anthropic 自己也承认 Opus 4.7 的安全表现「并非完全理想」。
  • Untested moat thesis at enterprise scale
    护城河论断在企业规模上未经检验
    The switching-cost erosion claim ignores that enterprise SaaS lock-in is driven by compliance audits and procurement cycles (24-36 months), which technical migration ease doesn't touch — the thesis is a bet, not yet a result.
    切换成本会崩塌的论断忽视了企业 SaaS 的锁定效应主要来自合规审计和采购周期(24 到 36 个月),技术迁移难度的降低并不能触及这一层——这仍是一个赌注,而非已验证的结果。
Bottom line
总评

Read this for the most concrete public account yet of what "agent-native" daily engineering work actually looks like — the Loop workflow and the organizational-process argument are genuinely instructive. Treat the "coding is solved" and "SaaS moats are collapsing" claims as bets made from inside a highly favorable sample (Anthropic itself, TypeScript/React), not as settled findings — the piece's own fact-checks on literacy statistics and the April 2026 database-deletion incident are reasons to discount the most sweeping predictions.

值得读,因为这是目前公开渠道里对「Agent 原生」日常工程工作最具体的描述——Loop 工作流和「优势在组织流程」的论断都相当有启发性。但「编程已被解决」和「SaaS 护城河正在崩塌」这类判断,应该被当作站在极度有利样本(Anthropic 自己、TypeScript/React)里做出的赌注,而非已经验证的结论——文中自带的识字率数据核查和 2026 年 4 月数据库删除事件,都是对最激进预测打折扣的理由。

06

Excerpt原文节选

This is a short excerpt, not the full piece — the complete essay belongs to its original author; please read it in full at the link above.

以下仅为节选,并非全文——完整文章版权归原作者所有,请点击上方链接阅读全文。

The English text on this side is an AI translation provided for convenience; the authoritative version is the source in the other language.

Boris Cherny is the creator of Claude Code inside Anthropic — he started with a three-person incubation team and took the idea from "press Tab to autocomplete a line of code in your IDE" all the way to "let an Agent write the whole project." By early 2026, Claude Code had surpassed a billion dollars in annualized revenue, something Anthropic itself has called "the fastest a product has ever gone from research preview to a billion dollars."

This interview is from Sequoia's 2026 AI Ascent conference, hosted by Sequoia partner Lauren Reeder.

Original video: https://www.youtube.com/watch?v=SlGRN8jh2RI

Key takeaways

Boris hasn't written a single line of code all through 2026 — he merges dozens of PRs a day, with a single-day record of 150, though he admits this is "to see how far the model can go."

Claude Code had no product-market fit for its first six months — when it first shipped, Boris himsel…

[…the source continues — read the rest at the link above]

[……原文更长,完整内容请点击上方链接阅读]

Anthropic's real lead isn't technical — it's organizational process: everyone has access to the models, but what matters is how you restructure your organization internally, how Claud…

Boris Cherny 是 Anthropic 内部 Claude Code 的创建者,从一个三人小团队的孵化项目做起,把“在 IDE 里按 Tab 自动补全一行代码”这件事彻底升级成“让 Agent 把整个项目写完”。Claude Code 在 2026 年初已经超过十亿美元年化营收,被 Anthropic 自己称为“史上从研究预览到十亿美元产品最快的一次”。

这次访谈来自 Sequoia 2026 年的 AI Ascent 大会,主持人是红杉合伙人 Lauren Reeder。

原始视频: https://www.youtube.com/watch?v=SlGRN8jh2RI

要点速览

Boris 整个 2026 年没写过一行代码 ,每天合并几十个 PR,单日记录是 150 个,但他承认这是“为了试试模型能跑多远”。

Claude Code 早期半年没有 PMF ,做出来时 Boris 自己只用它写 10% 的代码,是 Opus 4 在 2025 年 5 月发布之后才开始指数增长,每一代新模型都让曲线再往上拐一下。

Boris 现在大部分工作从手机完成 ,Claude App 里常驻 5 到 10 个 session、几百个 Agent,夜里有几千个在跑深度任务,核心调度模式叫 Loop,做法是让 Claude 通过 cron 起一个定时循环。

Anthropic 内部已经没有手写代码 :所有 SQL、所有产品代码都由模型生成,员工的 Claude 之间通过 Slack 互相沟通,把对方的不确定问题直接 ping 过去问。

关于“SaaS 的终结” ,Boris 借用 Hamilton Helmer 的“七种护城河”框架:切换成本和流程效力这两种会被 AI 抹平,因为模型可以帮你迁移、可以自己迭代流程;网络效应、规模经济、独占资源这些不变。

他给出的最重要历史类比是印刷术 ,认为软件构建会像识字一样普及,最合适写会计软件的是会计师而不是工程师,因为编程是简单部分,懂业务才是难的部分。

Anthropic 的真正领先不在技术 ,在组织流程:模型大家都能用,但内部组织怎么改造、Claud…

[…the source continues — read the rest at the link above]

[……原文更长,完整内容请点击上方链接阅读]