Feb 19, 2026 · 1h 27m · lennys-podcast
Head of Claude Code: What happens after coding is solved | Boris Cherny
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Anthropic's Head of Claude Code, Boris Cherny, explains how automated code generation and autonomous agentic workflows are eliminating manual syntax writing and transforming traditional software engineers into interdisciplinary builders. He shares key AI-native organizational strategies, tactical tips for multi-agent orchestration, and Anthropic's multi-tiered safety architecture.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 23.9% of the talking time here. How this is scored →
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Boris firmly dismisses the common developer impulse to box models into rigid multi-step pipelines, asserting that bespoke scaffolding is wiped out by next-generation models.
Hardest push from Lenny ▶ 3:55 Pressing on Cursor departure and swift returnLenny directly confronts Boris with a 'spicy question' demanding an explanation for why he abruptly left Anthropic for competitor Cursor before returning two weeks later.
Biggest teaching moment ▶ 57:25 Explaining mechanistic interpretability and superpositionBoris delivers an in-depth breakdown of how safety teams directly inspect internal model cognition and neuron superposition rather than relying solely on black-box evaluation.
Lenny holds their own ▶ 44:45 Presenting proprietary audience survey on AI sentimentLenny counters the purely optimistic narrative by introducing empirical poll data showing designers report significantly lower enthusiasm for AI tooling compared to engineers and PMs.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| The Cursor Detour and Returning to Anthropic's Mission | 4 | 3 | 1 | 2 | Lenny opens with an inquisitive and mildly provocative question regarding Boris's brief departure to Cursor before returning to Anthropic. Boris transparently explains his core motivation around safety, while Lenny cites industry stats on Claude Code adoption. | |
| Prototyping Claude Code and Terminal Interface Origins | 3 | 5 | 1 | 1 | Boris narrates the origin story of Claude CLI, sharing how unexpected model capabilities with the bash tool prompted him to build a terminal-based prototype. Lenny listens attentively as Boris details product discovery and initial internal traction. | |
| Thinking in Exponentials and Fostering Innovation | 4 | 4 | 1 | 1 | Lenny highlights how rapidly industry consensus shifted on AI-written code, referencing Peter Thiel/OpenAI comparisons. Boris explains Anthropic's culture of exponential extrapolation from scaling laws. | |
| The Reality of 100% Automated Code Generation | 3 | 5 | 1 | 2 | Lenny expresses surprise that Boris writes zero manual code while shipping dozens of PRs daily as a team lead. Boris details his workflow and explains that software engineering has shifted toward proactive task discovery. | |
| Massive Productivity Multipliers and Overcoming Legacy Habits | 4 | 5 | 1 | 1 | Boris provides concrete comparisons to his previous developer productivity work at Meta, noting 200% PR gains compared to legacy single-digit improvements. He illustrates how legacy engineering habits can hinder optimal agent utilization during debugging. | |
| Organizational Principles: Underfunding and Token Abundance | 5 | 4 | 1 | 2 | Lenny probes Boris's counterintuitive management philosophy of deliberate underfunding. Boris explains that token abundance coupled with lean headcount forces teams to automate aggressively rather than premature cost cutting. | |
| The Craft of Programming: Utility vs. Pure Artistry | 4 | 4 | 2 | 2 | Lenny asks whether Boris mourns the lost craft of manual coding. Boris reflects on his pragmatic view of software as utility, while acknowledging the enduring artistic appeal of low-level programming for some engineers. | |
| The Printing Press Analogy and Democratized Creation | 4 | 5 | 1 | 1 | Boris draws a detailed historical parallel between the Gutenberg printing press and AI software creation, predicting that manual syntax familiarity will soon be obsolete. Lenny reinforces the insight with his own experience as a former engineer. | |
| The Expansion of Agentic AI Across Tech and Society | 4 | 4 | 1 | 2 | Lenny raises the economic and societal implications of AI on knowledge work, invoking Jevons paradox. Boris clarifies the precise technical definition of an agent and notes the profound shift from conversational chat to autonomous tool execution. | |
| The Rise of the Curious Generalist Builder | 4 | 4 | 2 | 1 | Boris outlines how rigid specialized roles like PM, designer, and engineer are collapsing into the versatile 'builder'. Lenny observes the changing organizational landscape and seeks practical advice for future workers. | |
| Sponsor Message: MetaView | 5 | 2 | 0 | 1 | Lenny shares proprietary survey data from his social channels comparing job satisfaction across PMs, engineers, and designers after adopting AI. Boris engages with the findings and describes internal designer workflows. | |
| The Power of Latent Demand in Product Design | 4 | 5 | 1 | 1 | Boris explains the product concept of latent demand, citing Facebook Marketplace and non-engineers repurposing Claude Code's terminal for data science and bio-analysis. He connects this to designing AI systems aligned with model distribution. | |
| Rapid Iteration on Cowork and Three-Tiered Safety | 4 | 5 | 1 | 1 | Boris describes building Cowork within 10 days using Claude Code and breaks down Anthropic's three-tier safety framework: mechanistic interpretability, evals, and real-world deployment. Lenny listens to the rapid deployment strategy. | |
| Mechanistic Interpretability and Open Safety Standards | 4 | 5 | 1 | 1 | Boris delves into mechanistic interpretability, neural superposition, and Anthropic's open-source sandbox approach. Lenny actively validates the concepts and notes his interest in hosting deeper safety discussions. | |
| Continuous Agent Orchestration and Shared Roots | 5 | 3 | 1 | 1 | Lenny and Boris discover they were both born in Odesa, Ukraine, sharing personal reflections on migration and programmer heritage. Boris discusses running multiple asynchronous agents continuously. | |
| Principles for AI Builders: The Bitter Lesson and Future Models | 4 | 5 | 2 | 1 | Boris synthesizes architectural principles from Rich Sutton's 'The Bitter Lesson,' cautioning against brittle prompt scaffolding and advising founders to build for models six months in the future. Lenny asks clarifying questions on what capabilities to assume. | |
| Pro Tips for Mastering Claude Code | 3 | 5 | 1 | 1 | Boris gives tactical user recommendations for Claude Code, detailing how 'plan mode' operates via minimal prompt steering and why selecting maximum effort on frontier models reduces total token spend. | |
| Market Competition, Post-AGI Aspirations, and Miso Making | 4 | 4 | 1 | 1 | Lenny inquires about competitive dynamics with OpenAI Codex and brings up a prompt from co-founder Ben Mann regarding Boris's post-AGI lifestyle. Boris details his artisanal miso making and long-term mindset. | |
| Anthropic's Long-Term Vision and User Feedback Loops | 4 | 4 | 1 | 1 | Boris underscores Anthropic's long-term vision connecting coding, tool use, and computer use. Lenny cites reported revenue figures and the massive scale achieved within a single year. | |
| Lightning Round: Essential Reading and Sci-Fi Inspirations | 4 | 3 | 1 | 1 | In the lightning round, Boris recommends seminal technical and sci-fi books including Functional Programming in Scala, Accelerando, and Wandering Earth. Lenny matches Boris with recommendations of his own. | |
| Lightning Round: Favorite Products, Podcasts, and Custom Evals | 5 | 3 | 1 | 1 | Boris explains his workflow with Cowork and reveals that Anthropic utilized Lenny's published newsletter posts as an internal evaluation benchmark. Lenny reacts playfully to becoming an AI evaluation metric. |