← all video summaries
Fireside chat

Boris Cherny on Claude Code and the End of Hand-Written Code

The creator of Claude Code on why he hasn't written a line of code in 2026, why coding is "solved" for him, and what a printing-press-scale shift does to teams, startups, and software itself.

Watch on YouTube
TL;DR

The short version

  1. Claude Code started as a pre-PMF bet inside Anthropic Labs, built for a model that didn't exist yet — and was barely usable for its first six months until Opus 4 in May.
  2. The model now writes 100% of Boris's code; he ships dozens of PRs a day, hit 150 in one day, and does most of his work from his phone.
  3. /loop" — Claude scheduling a recurring cron job to babysit PRs, keep CI healthy, or cluster feedback — is the part of his setup he reaches for most.
  4. As writing code gets 10–100x cheaper, switching costs and process power fade as moats while network effects and scale economies hold; expect 10x more disruptive startups.
  5. The closest historical parallel is the printing press: software is about to become a literacy anyone has, and the best person to build accounting software is a great accountant, not an engineer.

01 · Origin

A pre-PMF bet on the next model

Claude Code came out of Anthropic Labs, a small incubator team Boris joined in late 2024 — the same group that shipped MCP and the desktop app. The premise was a "product overhang": the model could already do things no product had captured. In late 2024 the state of the art in coding was type-ahead — open your IDE, press tab, complete one line. Sonnet 3.5 had just made that work. The bet was that the model was nearly ready to skip type-ahead entirely and write all the code itself.

Boris Cherny, creator of Claude Code, at Sequoia's AI Ascent. The team built for a model that wouldn't exist for six months.00:02:50
We were trying to build this thing that was pre-PMF, and we knew it wouldn't have PMF for six months because we were building for the next model.— Boris Cherny

For the first six months it barely worked — Boris used it for maybe 10% of his code. Even at launch it wasn't a hit. The exponential growth started with Opus 4 in May, and re-inflected with every release after: 4.5, 4.6, 4.7.

02 · Coding is solved

100% of the code, on distribution

Boris's answer to "is coding solved" is unambiguous for himself: it's 100%. The model writes all of his code, and has since roughly October or November of last year. The Claude Code codebase — which leaked, so it's no secret — is just TypeScript and React. That choice was deliberate: early on, when the model was weaker, picking a language and framework "on distribution" mattered a lot. Today the model can pick up languages and frameworks it hasn't seen.

"For me it's just solved." Boris ships a few dozen PRs a day — and once did 150 in a single day, just to see how far he could push it.00:06:24
The caveat"Solved" is true for his codebase, not everywhere. Very large codebases and weirder languages the model isn't good at yet are still hard. The usual answer: wait for the next model.

03 · The setup

Sessions, sub-agents, and /loop

Most of Boris's work now happens on his phone, through the Claude app's code tab — typically five to ten sessions running at once, each with a batch of agents underneath. A few hundred agents during the day, a few thousand overnight doing deeper work.

The piece he reaches for most isn't sub-agents — it's /loop.00:08:00

The tool he keeps coming back to is /loop: Claude uses cron to schedule a recurring job — every minute, every few minutes, every day. He runs dozens of them.

Babysit PRs

One loop fixes CI and auto-rebases his open pull requests.

Keep CI healthy

Another watches for flaky tests and goes and fixes them.

Cluster feedback

A third pulls feedback off Twitter and clusters it for him every 30 minutes.

I sort of feel like loops are the future at this point.— Boris Cherny

Anthropic also just launched routines — the same idea, but running on the server, so it keeps going after you close your laptop.

04 · Teams

Everyone codes, across disciplines

Boris's prediction for teams: many more generalists, and increasingly cross-disciplinary ones. Today a generalist usually still means an engineer who spans iOS, web, and server. What he sees coming is generalists who are strong in product engineering and design, or product and data science and engineering at once.

On the Claude Code team, the engineering manager, PM, designers, data scientist, finance person, and user researcher all write code.00:13:04
On his own teamEveryone on the Claude Code team codes. They're each a specialist in something — but now everyone is also coding.

05 · The SaaS question

Which moats survive

Asked whether cheaper code means a "SaaS apocalypse," Boris reaches for the Acquired podcast's framing of Hamilton Helmer's seven powers. His read: AI weakens some moats and leaves others intact. Switching costs erode — you can use the model to port from one tool to another. Process power erodes too, because Claude is getting good at figuring out process; with 4.7 you can hand it a target and tell it to iterate until done.

Boris with interviewer Lauren Reader. The older moats — network effects, scale economies, cornered resources — he thinks hold.00:12:58

The second shift: he expects the number of startups that "disrupt everything" to rise roughly 10x over the next decade. A tiny startup can now build something as valuable as a large company and compete head-to-head — because the incumbent has to evolve its processes, retrain its people, and fight internal resistance, while a fresh team can build AI-native from the ground up.

It's the best time to build. It's the best time to be a startup. There's so much disruption coming.— Boris Cherny

06 · The printing press

Software as literacy

Boris's clearest historical parallel is the printing press in 1400s Europe. Before it, about 10% of Europeans were literate — often employed to read and write for kings and lords who couldn't. In the 50 years after the first press, more was published in Europe than in the prior thousand years, and the cost of a book fell roughly 100x. Literacy eventually climbed toward 70% globally — though it took a couple hundred years and required schools and governments.

"Software will be a thing that is fully democratized, that anyone can do" — and faster than 50 years.00:15:40

A corollary he draws: the best person to write accounting software is a great accountant, not an engineer — because the domain is the hard part and the coding is the easy part.

You don't need a degree in reading and writing to know how to read and write. Although still there are professional writers.— Boris Cherny

07 · Looking ahead

What he'd build now

Pressed for the shape of a product he'd build today that gets more interesting as models improve in 6–12 months, Boris points to Claude design — already decent, about to get much better — plus more Claude Code launches landing in the coming weeks, and the broader push around massively parallelizing agents through loop and batch. Computer use is the other one he keeps naming: slow today, but with 4.7 it can drive nearly any piece of software on your machine, and Anthropic believes it's well ahead there.

A fireside chat at AI Ascent — and a window into how Anthropic already works internally: no manually written code anywhere, Claudes coordinating over Slack.00:00:43
The throughlineOn local-vs-cloud, harness-vs-model, MCP-vs-computer-use — Boris keeps landing on the same answer: it won't be the engineer's decision much longer. The model will start the agents, build the environments, and pick the tools. To the model, it's all just tokens.