Boris Cherny
公开发言整理
Claude Code 创始人兼负责人。涵盖他在 Twitter/X、播客、采访中关于产品哲学、工作流、软件工程未来的所有公开发言,按主题分类整理。
01 人物背景
身份
Claude Code 创始人兼负责人(Creator & Head)at Anthropic
著作
《Programming TypeScript》O'Reilly 出版
Cursor 插曲
曾短暂加入 Cursor,两周后回归 Anthropic
现职
同时负责 Claude Code + Cowork(企业 AI 协作产品)
02 Claude Code 的诞生故事
"When I first started Claude Code, it was just going to be a little hack. I had no idea that this thing would be useful at all."
Claude Code 最初只是一个简单的终端原型(terminal-based prototype),不是经过精心规划的大项目,而是一个快速 hack 演变而来的工具。内部公告只收到 2 个赞——没人相信命令行工具会成功。
4%
GitHub 公开 commit
2x
上月 DAU 翻倍
$1B
年化 ARR
🔁 Cursor 插曲的意义
Boris 曾离开 Anthropic 去 Cursor,仅两周就返回。他的解释:"Whatever the work might be, no matter how exciting — it's just not a substitute for the mission."
安全使命是 Anthropic 每个人留下来的唯一原因——Boris 自己验证了这一点。
03 产品哲学
满足「潜在需求」,而非用户说出口的需求
Claude Code 的成功来自挖掘用户没有明确表达、但真实存在的需求(Latent Demand),而不是照着用户反馈单做。用户说"我要更快的马",但真正的需求是"更快地到达目的地"。
验证循环是核心
"Probably the most important thing to get great results out of Claude Code — give Claude a way to verify its work. If Claude has that feedback loop, it will 2-3x the quality of the final result."
Compounding Engineering — 每个错误都是一条规则
"Anytime we see Claude do something incorrectly we add it to the CLAUDE.md, so Claude knows not to do it next time."
Code review 时 tag @claude,让 Claude 自己把规则写进 CLAUDE.md。团队合作越久,AI 越智能。(概念来自 Dan Shipper)
04 对软件工程未来的判断
"Coding is Solved"
不是"不需要程序员了",而是:写代码本身不再是瓶颈。软件工程师的角色将从"写代码的人"演变成"指挥 AI 舰队的人"。
"The tools to multiply human output by a factor of five are already here. They require only a willingness to stop thinking of AI as an assistant and start treating it as a workforce."
🎮 Starcraft 比喻
传统开发 = 内循环(写函数 → 测试 → 写下一个)。新方式 = 像打星际争霸,你是战略指挥官,管理多支 AI 并行部队。一个人 = 一个小型工程部门的产出。
🏢 Spotify 案例(2026年2月)
Spotify 最好的开发者自 2025年12月起没写过一行代码。Boris 认为这个转型对工程师群体是真实冲击——不是"被淘汰",而是"角色重新定义"。
05 工作流与技术实践
来源:@bcherny X thread(2026-01-02 & 2026-01-31)
并行代理工作流
终端
5 个 Claude Code 实例,分 5 个 tab(编号 1-5)
每个 tab 独立 git worktree,避免冲突
浏览器
同时跑 5-10 个 claude.ai/code session
早上手机 iOS 启动,电脑接力
~/repo-1 $ ~/repo-2 $ ~/repo-3 $ ~/repo-4 $ ~/repo-5 $
模型选择:永远用最慢最强的
"I use Opus 4.5 with thinking for everything. It's the best coding model I've ever used, and even though it's bigger & slower than Sonnet, since you have to steer it less and it's better at tool use, it is almost always faster than using a smaller model in the end."
CLAUDE.md:团队共享的 AI 记忆
# CLAUDE.md
**Always use `bun`, not `npm`.**
bun run typecheck
bun run test -- -t "test name"
bun run lint:file -- "file1.ts"
# PR 中动态更新:
nit: use string literal, not ts enum
@claude add to CLAUDE.md to never use enums,
always prefer literal unions
整个团队每周多次贡献内容,code review 时让 Claude 自己更新规则。
Plan Mode 工作流
团队变体:Claude A 写计划 → Claude B 以 staff engineer 角色审计划。
Slash Commands & Subagents
最常用命令
/commit-push-pr
一键:commit → push → 开 PR。存于 .claude/commands/
子代理目录
PostToolUse Hook — 自动格式化
"PostToolUse": [{
"matcher": "Write|Edit",
"hooks": [{
"type": "command",
"command": "bun run format || true"
}]
}]
工具集成(MCP)
Slack MCP
搜索 / 发帖
BigQuery
bq CLI 跑查询
Sentry
抓错误日志
RAG 的取舍
"We did RAG early on then unshipped it for a number of reasons: privacy, security, reliability, index staleness. Overall, we found that agentic search gave better results with fewer tradeoffs."
Auto Mode(2026-03 新功能)
"New in Claude Code: auto mode. Instead of approving every file write and bash command, or skipping permissions entirely, auto mode lets Claude make permission decisions on your behalf. Safeguards check each action before it runs."
06 团队管理与组织设计
「故意欠配置」策略(Intentional Underfunding)
Claude Code 团队刻意保持小规模——不是资源不足,而是有意为之。小团队被迫更创造性地使用 AI 工具;给团队无限 token 额度,让他们充分体验自己做的产品。
与 Anthropic 总裁 Daniela Amodei 的"Do more with less"战略一致
工程师 = 产品最重度用户
Boris 的整个工作流本身就是一个活广告。Claude Code 团队是自己产品的最重度用户,产品决策直接来源于真实使用体验。
07 核心原则
Boris 在 Lenny's Podcast 中分享的团队工作原则(详见下方「Lenny's Podcast 完整摘录」章节):
验证循环优先
给 Claude 一种验证自己工作的方式,这是获得好结果最重要的事。带来 2-3x 的质量提升。
CLAUDE.md 是团队的共同记忆
每个错误都是一条规则,持续迭代。团队合作越久,AI 越智能——这就是 Compounding Engineering。
计划比实现更重要
在 Plan mode 投入精力,让 Claude 一次性实现。事情跑偏时不要硬推——退回 Plan mode 重新规划。
08 🎙️ Lenny's Podcast 完整摘录
来源:Lenny's Podcast「Head of Claude Code — What happens after coding is solved」(2026年3月)· 逐字稿整理
Claude Code 诞生故事
"When I first started Claude Code, it was just going to be a little hack. We broadly knew at Anthropic that we wanted to ship some kind of coding product. I spent one month hacking, built a bunch of weird prototypes, most of them didn't ship. Then I spent a month doing post-training to understand the research side. Then I came back and just started prototyping what eventually became Claude Code."
"The very first version — I have a video recording. It was called ClaudeCLI back then. I gave it a bash tool and it just was able to use that to write code to tell me what music I'm listening to when I asked it. And this is the craziest thing — I didn't instruct the model to say use this tool for this. The model was given this tool and figured out how to use it to answer a question I wasn't even sure it could answer."
内部发布的"2 个赞"时刻
Boris 在内部发布了 Claude Code 的公告,只收到 2 个赞——因为大家认为 coding 工具应该是 IDE,没人觉得终端版会有用。他选择继续坚持,因为"你找到一条线,就必须去拉它"。
"The team was called the Anthropic Labs team. We built Claude Code, we built MCP, we built the desktop app. You can see the seeds of this idea: coding, then tool use, then computer use — this has been our belief as a company for a long time."
"The biggest reason we stuck with the terminal was the model is improving so quickly. We felt there wasn't really another form factor that could keep up with it."
"Coding is Solved" — 原话
"I think at this point it's safe to say that coding is largely solved. At least for the kind of programming that I do, it's just a solved problem because Claude can do it."
"Over the next few months I think what we're going to see is across the industry it's going to become increasingly solved — for every kind of codebase, every tech stack that people work on."
"100% of my code is written by Claude Code. I have not edited a single line by hand since November. Every day I ship 10, 20, 30 PRs. At the moment I have five agents running while we're recording this."
"Software Engineer" 头衔将消失
"I do think that there's a future where — I think by the end of the year — what we're going to start to see is these start to get murkier. In some places the title software engineer is going to start to go away. It's just going to be replaced by 'builder', or maybe it's just everyone's going to be a product manager and everyone codes."
"On the Claude Code team, everyone codes. Our product manager codes, our engineering manager codes, our designer codes, our finance guy codes, our data scientist codes. Everyone on the team codes."
活字印刷机比喻
"In the mid-1400s, literacy was actually very low — sub 1% of the population. It was scribes who did all the writing. They were employed by lords and kings. Then Gutenberg and the printing press came along, and in the 50 years after, more printed material was created than in the thousand years before. The cost went down 100x. Literacy went up to 70% globally over the next 200 years."
"There was actually a historical document — an interview with a scribe in the 1400s. They were actually very excited about the printing press. They said: 'The thing I don't like doing is copying between books. The thing I do like is drawing the art and book binding. I'm really glad my time is freed up.' As an engineer I feel a parallel — I don't have to do the tedious work of coding anymore. The fun part is figuring out what to build, talking to users, thinking about big systems."
"I imagine a world a few years in the future where everyone is able to program. Anyone can just build software anytime. And I have no idea what that unlocks. It's just the same way that in the 1400s, no one could have predicted the Renaissance."
Cowork 产品 — 是什么、为谁而建
"Co-work is kind of the first way to get at this — bringing agentic AI to people who haven't really used it before. When I think back to engineering a year ago, no one really knew what an agent was. But nowadays it's just the way we do our work. For non-technical folks today, all they've used is conversational AI — a chatbot. No one has really used an agent before. Co-work might be the first time they're using something that actually acts."
10 天内从 0 到百万用户
Cowork 在 10 天内完全用 Claude Code 构建,包含完整的虚拟机沙箱安全系统。发布后比 Claude Code 早期增长快得多。Boris:"Claude Code 发布时不是立即爆红,Cowork 发布时是。"
"I had to pay a parking ticket the other day. I just had co-work do it. All of my project management for the team — co-work does all of it. It's syncing stuff between spreadsheets, messaging people on Slack and email."
潜在需求(Latent Demand)— 完整阐释
"Latent demand is this idea that if you build a product in a way that can be hacked or misused by people in a way it wasn't really designed for — to do something that they want to do — then this helps you as the product builder learn where to take the product next."
Facebook Marketplace 案例
40% 的 Facebook 群组帖子是买卖交易。没有人为此设计产品,但用户自发"滥用"了群组功能。这就是潜在需求——当你看到这个信号,就知道要为此专门造一个产品。
Claude Code 的非技术用户奇观
Boris 发现大量用户用 Claude Code(一个命令行工具)做完全非技术的事情:种番茄、分析基因组、从损坏硬盘恢复婚礼照片、分析 MRI 影像。这直接催生了 Cowork。
"I remember walking into the office and our data scientist Brendan had Claude Code on his computer — just a terminal up. I was shocked. He figured out how to open the terminal, downloaded Node.js, downloaded Claude Code, and was doing SQL analysis in a terminal. The next week all the data scientists were doing the same thing."
"The modern framing I've been seeing in the last 6 months: look at what the model is trying to do and make that a little bit easier. For Claude Code, we inverted the approach — the product is the model. We want to expose it. Put the minimal scaffolding around it. Let it decide which tools to run and in what order."
故意欠配置 + 无限 Token 策略
"There's this interesting thing that happens when you underfund everything a little bit — people are forced to use Claude. For work where sometimes we just put one engineer on a project, the way they're able to ship really quickly is because they want to ship quickly. And if you have Claude, you can just use that to automate a lot of work."
"My advice generally: don't try to cost cut at the beginning. Start by just giving engineers as many tokens as possible. We're starting to see 'unlimited tokens' come up as a perk at some companies. At the beginning you just want to throw a lot of tokens at it and see if the idea works and give engineers the freedom to do that."
"At Anthropic we're starting to see some engineers spending hundreds of thousands a month in tokens."
为什么离开 Anthropic 去 Cursor,又两周后回来
"I joined Cursor because I'm a big fan of the product. Honestly I met the team and was just really impressed. They're an awesome team. They saw where AI coding was going before a lot of people did. The idea of building good product was very exciting for me."
"As soon as I got there, what I started to realize is what I really missed about Anthropic was the mission. If you ask anyone at Anthropic why they're here, the answer is always going to be safety. This mission-drivenness just really resonated with me. And I just know personally it's something I need in order to be happy. Whatever the work might be, no matter how exciting — even building a really cool product — it's just not really a substitute for that."
他分享给每个新成员的原则
在 Lenny's Podcast 中 Boris 提及的团队核心原则(原文摘录):
欠配置一点点(Underfund slightly)
"When you underfund things a little bit, people are forced to use Claude. This is something we see over and over."
能今天做的事,今天就做(Ship today, not tomorrow)
"If you can do something today, you should just do it today. Early on it was really important because it was just me — our only advantage was speed. If you want to go faster, a really good way is to just have Claude do more stuff."
Build for the model 6 months from now(为 6 个月后的模型而建)
"This is advice I give to a lot of folks, especially people building startups. It's going to be uncomfortable because your product-market fit won't be very good for the first 6 months. But if you build for the model 6 months out, when that model comes out you're just going to hit the ground running."
注:在播客中 Boris 还提到"best thing you can do is have Claude do it"作为团队口头禅,以及"bitter lesson"(更通用的模型总会打败特化模型)作为产品决策依据。
通才在 AI 时代的优势
"Try to be a generalist more than you have in the past. Some of the most effective engineers I work with every day — they cross over disciplines. Some of the strongest engineers are hybrid product and infrastructure engineers, or product engineers with really great design sense, or an engineer with a really good sense of the business, or an engineer that loves talking to users."
"A lot of the people that will be rewarded the most over the next few years won't just be AI native. They're curious, they're generalists, they cross over multiple disciplines and can think about the broader problem they're solving — rather than just the engineering part of it."
安全与 ASL-4 — 为什么安全是一切的核心
"There are three layers of safety. The lowest level is alignment and mechanistic interpretability — when we train the model, we want to make sure it's safe. We have pretty sophisticated technology to understand what's happening in the neurons, to trace it. If there's a neuron related to deception, we're starting to get to the point where we can monitor it. The second layer is evals — a laboratory setting, the model in a petri dish. The third layer is seeing how the model behaves in the wild."
"Opus 4 was our first ASL-3 class model. We just saw this inflection — everyone started to use Claude Code for the first time and our growth really went exponential."
"We released Claude Code really early because we wanted to study safety. We used it within Anthropic for 4 or 5 months before we released it — we weren't sure if it was safe. This was the first big agent that folks had released at that point."
所有电脑工作的未来
"It's going to be a lot of the roles adjacent to engineering — product managers, design, data science. It is going to expand to pretty much any kind of work you can do on a computer, because the model is just going to get better and better at this. An agent is an LM that's able to use tools. It doesn't just talk, it can actually act. It can use your Google docs, send email, run commands on your computer. Any kind of job where you use computer tools — I think this is going to be next."
"Models are running for very long periods of time now. With Sonnet 3.5 a year ago, it could run maybe 15-30 seconds before going off the rails. Nowadays with Opus 4.6, it'll run maybe 10-30 minutes unattended. Some have run for hours or even days. I think over time this is going to become more and more normal."
给感到不安的人的建议
"Experiment with the tools, get to know them, don't be scared of them. Just dive in, try them, be on the bleeding edge, beyond the frontier. Maybe the second piece of advice is try to be a generalist more than you have in the past."
"I have never enjoyed coding as much as I do today because I don't have to deal with all the minutia."
他的 motto:Common Sense
"Use common sense. A lot of the failures I see in a work environment is people failing to use common sense — they follow a process without thinking about it, or they're working on a product that's not a good idea and they're just following the momentum. The best results are people thinking from first principles and developing their own common sense. If something smells weird, it's probably not a good idea."
09 来源
播客 · 2026年3月
Lenny's Podcast: Head of Claude Code — What happens after coding is solved ↗
X Thread · 2026-01-02
@bcherny 的 13 条工作流 tips ↗
X Thread · 2026-01-31
@bcherny 的 10 条团队 tips ↗
X · 2026-03-12
Auto Mode 公告 ↗
VentureBeat · 2026年1月
The creator of Claude Code just revealed his workflow ↗
社区整理
howborisusesclaudecode.com ↗