Skip to main content
podcastFebruary 19, 2026

Head of Claude Code: What happens after coding is solved

Guest: boris-chernyHosted by Lenny Rachitsky

Coding is a solved problem — the bottleneck shifts to taste, product sense, and deciding what to build. Boris Cherny makes the case that underfunding teams, betting on general models, and building for the model six months out is how you win.

Timestamps

TimeTopic
0:00Cold open
4:00Boris's brief move to Cursor and return to Anthropic
8:00Origin story of Claude Code — from two-like hack to platform
14:00Growth: 4% of all GitHub commits, exponential acceleration
17:00100% AI-written code since November
20:00Next frontier: Claude generating ideas from feedback and telemetry
22:00Coding as "largely solved" — expansion into Co-Work
25:00Latent demand: the Facebook Marketplace analogy
30:00200% productivity increase per engineer at Anthropic
33:00Product advice: the bitter lesson, build for model N+1
38:00Printing press analogy — democratization of programming
42:00Role evolution: "builder" replaces "software engineer"
46:00Three layers of AI safety
50:00Tips for using Claude Code effectively
55:00Co-Work usage patterns
58:00Lightning round: books, life motto, post-AGI plans

Key Arguments

Coding Is Solved (~17:00)

Boris hasn't edited a single line of code by hand since November. 100% written by Claude Code. He ships 10-30 PRs per day. The claim isn't provocative for effect — he means it literally. The remaining challenge is upstream: deciding what to build, reviewing output, and ensuring safety. This maps exactly to what shipping-at-inference-speed describes — output is bottlenecked by inference time, not developer skill.

Underfunding Drives Innovation (~30:00)

Put one engineer on a project and give them unlimited tokens rather than staffing up. At Anthropic, productivity per engineer increased 200% — confirming the numbers from how-ai-is-transforming-work-at-anthropic. The intrinsic motivation to ship fast, combined with AI leverage, outperforms larger teams. Boris frames this as deliberate under-resourcing, not austerity.

The Bitter Lesson Applied to Product (~33:00)

Borrowing Rich Sutton's principle: always bet on the most general model. Scaffolding and rigid workflows may improve performance 10-20%, but those gains get wiped out with the next model generation. Give the model tools and a goal, let it figure out the execution. This is the anti-pattern to over-engineering your AI workflows — the model will outgrow your guardrails.

Build for Model N+1 (~33:00)

Design your product architecture for the capabilities the next model will have, not current limitations. Claude Code was built this way: early versions wrote only 20% of Boris's code, but the architecture was ready when Opus arrived. Accept poor product-market fit early in exchange for explosive fit when the model catches up.

Latent Demand as Product Signal (~25:00)

When users abuse your product for unintended purposes, you've found what to build next. Claude Code users were analyzing genomes, recovering wedding photos, growing tomato plants — from a terminal. This directly led to building Co-Work (see first-impressions-of-claude-cowork-anthropics-general-agent). The pattern mirrors Facebook Groups being used for buy/sell leading to Marketplace.

The Printing Press Analogy (~38:00)

Sub-1% literacy in 1450s Europe maps to sub-1% of the population knowing how to code today. The printing press produced more material in 50 years than the prior thousand years. Boris argues AI-generated code is following the same curve. Democratized programming will unlock outcomes as unpredictable as the Renaissance was to 15th-century scribes.

Generalists Win (~42:00)

The title "software engineer" is starting to disappear, replaced by "builder." On the Claude Code team, the PM codes, the designer codes, the finance person codes. The strongest contributors cross disciplines — product sense, design sense, business acumen all matter more than deep specialization. This extends what Boris described in boris-cherny-on-what-grew-his-career-and-building-at-anthropic about hiring generalists.

Predictions

  • ~20% of all GitHub commits by Claude Code by end of 2025 — Boris endorses the Semi Analysis projection, up from 4% currently
  • Engineers won't need an IDE to code — the terminal and AI agents replace the traditional editor
  • "Software engineer" title fades — replaced by "builder" as the default role description
  • Token costs will exceed salary costs — already emerging at Anthropic, where some engineers spend hundreds of thousands per month on tokens
  • Models will run autonomously for hours or days — not just minutes as today

Notable Quotes

"100% of my code is written by Claude Code. I have not edited a single line by hand since November." — Boris Cherny

"Don't try to box the model in... almost always you get better results if you just give the model tools, give it a goal, and let it figure it out." — Boris Cherny

"The title software engineer is going to start to go away. It's just going to be replaced by builder." — Boris Cherny

"From the very beginning, we bet on building for the model six months from now, not for the model of today." — Boris Cherny

Resources Mentioned

  • Functional Programming in Scala by Chiusano & Bjarnason
  • Accelerando by Charles Stross
  • The Wandering Earth by Liu Cixin
  • A Fire Upon the Deep and A Deepness in the Sky by Vernor Vinge
  • "The Bitter Lesson" by Rich Sutton — the foundational essay on betting on general methods
  • Acquired podcast — Nintendo episode recommended

Connections