# cherny-sequoia-coding-is-solved-loops-printing-press-2026-05

## Veille

Interview Boris Cherny (créateur Claude Code, Anthropic) lors d'un événement Sequoia (animateurs : Asia, Lauren Reader). Cherny déclare ***"coding is solved"*** : il écrit lui-même **0 ligne de code** depuis fin 2025, le modèle écrit **100%**, *"a few dozen PRs/day, 150 PRs in a single day record"*. Récit de la genèse Claude Code (Anthropic Labs incubator fin 2024, Mike Krieger en charge du round 2, build pre-PMF *"for the next model"*, première release non-décollante, **exponential growth démarré avec Opus 4 en mai 2025**, accéléré à chaque nouveau modèle 4 → 4.5 → 4.6 → 4.7). Setup personnel actuel : **"most of my work I do from my phone"** (iOS), 5-10 sessions, **"a few hundred agents going, a few thousand at night"**, **`/loop` est l'avenir** (cron + repeat jobs, agents qui babysittent CI, rebasent les PRs, clusterisent les feedbacks Twitter). **Routines** = équivalent serveur, laptop fermé. Vision SaaS : pas d'apocalypse, mais **réordonnancement du framework 7 Powers de Helmer** (switching costs ↓, process power ↓, network effects/scale economies/cornered resources inchangés) et **10× plus de startups disruptives** dans les 10 prochaines années. Analogie pivot : la **presse de Gutenberg** (10% de littéracie en 1400 → 70% en quelques siècles, livre 100× moins cher en 50 ans), *"software will be similarly democratized, but faster than 50 years"* — *"the best person to write accounting software is not an engineer, it's a really good accountant."*

## Titre Article

Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next

## Date

2026-05-05

## URL

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

## Keywords

Boris Cherny, Anthropic, Claude Code, Sequoia, Lauren Reader, Asia, coding is solved, Claude code psychosis, /loop slash command, routines server-side, cron repeat jobs, agents in loops, multi-session iOS workflow, exponential growth Opus 4 May 2025, Anthropic Labs incubator late 2024, Mike Krieger round 2, MCP desktop app team disbanded, pre-PMF "build for the next model", TypeScript React on-distribution, 100% code generated, few dozen PRs daily, 150 PRs single day record, cross-disciplinary generalists, every team member codes, SaaS apocalypse no, Hamilton Helmer 7 Powers, switching costs decline, process power decline, network effects scale economies cornered resources persist, 10x more startups disrupting, printing press analogy 1400s, literacy 10% to 70%, books 100x cheaper, "best person to write accounting software is an accountant", harness less important as model improves, prompt injection static verification permission modes, model just figures it out, agent-to-agent Slack communication, no manually written code Anthropic, MCP for knowledge work, computer use catchall, Claude Design coming, model vs harness 50-50

## Authors

Boris Cherny (créateur de Claude Code, Anthropic) interviewé par Lauren Reader (Sequoia) avec introduction d'Asia (Sequoia).

## Ton

**Profil** : Interview live au format conversationnel devant une audience de fondateurs/investisseurs/builders Sequoia (*"as a roomful of builders"*, applaudissements, sondages à main levée à plusieurs reprises). Format hybride keynote-Q&A avec 6 questions audience. Public présent : opérateurs, fondateurs, investisseurs early-stage Sequoia ; public diffusé : la communauté tech mondiale via YouTube Sequoia Capital. Cherny n'est plus à présenter dans cette audience — l'intro est essentiellement comique (*"Boris is the father of Claude Code"*, *"Claude code psychosis"*).

**Style** : Cherny parle décontracté, première personne, hésitations naturelles assumées (*"like"*, *"you know"*), vocabulaire de bâtisseur plutôt que d'évangéliste. Il alterne entre **anecdote chiffrée** (*"there was a day last week I did like 150 PRs in a day. That was a record"*), **récit d'origine vécue** (la genèse Claude Code racontée comme un mini-roman startup), **vision audacieuse** (*"coding is solved"*, *"SaaS apocalypse"* analyse) et **autodérision** (*"My team lovingly says I have Claude code psychosis"*, *"It's extremely embarrassing, so please don't search it"* à propos d'un guide BASIC TI-83 Plus écrit au collège).

**Métaphores travaillées** :
- ***"Product overhang"*** : *"the model can do all the stuff that no product has yet captured"* — concept central pour comprendre la stratégie Claude Code (build for the next model).
- ***"Coding is solved"*** : déclaration provocatrice à valeur d'aphorisme.
- ***"Loops are the future"*** : pivot conceptuel sur la nouvelle primitive d'architecture agentique.
- ***Analogie de la presse de Gutenberg*** (1400s, 10% littéracie → 70%, livre 100× moins cher en 50 ans) — la métaphore historique la plus structurante de l'intervention. *"Software will be similarly democratized, but faster than 50 years."*
- ***"The best person to write accounting software is not an engineer, it's a really good accountant"*** — phrase-pivot sur la démocratisation et le rééquilibrage domaine vs codage.

**Position épistémique** : Cherny refuse à la fois la prudence excessive (*"coding is solved"* est une déclaration radicale) et le triomphalisme béat (il pose des limites : *"this is not the case everywhere — there's very big complicated codebases, weird languages the model isn't good at yet"*). Il assume la **prédiction** comme exercice (*"I'm here to make predictions, so I'll try to make some"*) et structure ses prédictions par **frameworks établis** (Helmer's 7 Powers) plutôt que par speculation libre.

**Autorité** : construite par (a) la position institutionnelle (créateur Claude Code, lead du produit le plus discuté de l'écosystème agentique), (b) la **pratique radicale dogfoodée** (100% code généré, 150 PRs/jour record, setup iOS exclusif), (c) l'humilité narrative (récit du *"it just really didn't work for the first 6 months"*), (d) le rapport de force inversé avec l'audience (*"Show of hands, who here uses Claude Code?"* — la majorité des mains se lèvent, le speaker n'a plus à se légitimer).

## Pense-betes

- **Date / source** : interview vidéo Sequoia Capital (YouTube), URL https://www.youtube.com/watch?v=SlGRN8jh2RI. Date précise non visible dans le transcript ; références internes (*Opus 4.7* comme modèle courant, *"we also just launched routines"*) la situent **fin avril / début mai 2026**. Date d'ajout dossier veille : 2026-05-05.
- **Speaker** : **Boris Cherny**, créateur Claude Code, Anthropic. **Interviewer** : Lauren Reader (Sequoia). **Intro** : Asia (Sequoia).
- **Background Cherny révélé** :
  - YC alumni, premier employé d'une boîte YC, plusieurs startups passées.
  - Auteur d'un livre *"Programming TypeScript"*.
  - **N'a pas écrit une seule ligne de code en 2026** (déclaration faite à Sequoia avant l'interview).
  - Anecdote middle school : a écrit un guide BASIC pour TI-83 Plus, *"still on the internet, extremely embarrassing"*.
- **Ouverture comique** :
  - *"Show of hands, who here uses Claude Code?"* → majorité.
  - *"Show of hands, who here has Claude code psychosis?"* → rires.
  - *"My team lovingly says I have Claude code psychosis, which may or may not be true."*

### Histoire de Claude Code (récit nouveau)

- **Origine** : Cherny rejoint **Anthropic Labs** fin 2024 — incubator interne Anthropic, équipe de quelques personnes.
- **Output Anthropic Labs** : Claude Code, MCP, application desktop. Équipe **disbanded** une fois la mission accomplie.
- **Round 2 actuel** : équipe reformée, dirigée par **Mike Krieger** (Chief Product Officer Anthropic, ex-cofondateur Instagram).
- **Pourquoi Cherny a démarré coding** : *"product overhang"* — *"the model can do all the stuff that no product has yet captured."*
- **État de l'art coding fin 2024** : *"type ahead"* (open IDE, press tab, complete one line). C'est ce que Sonnet 3.5 avait débloqué.
- **Pari** : aller plus loin — *"the model was almost ready for the next big step. So we don't have to do type ahead anymore, we can just have the agent write all of the code."*
- **6 premiers mois** : *"it just really didn't work. It was like not very good. It was barely usable. I used it for maybe 10% of my code."*
- **Première release Claude Code** : *"It was not a hit. There's a lot of people that used it, but it did not have this exponential growth that it has today."*
- **Inflection point** : ***Opus 4 en mai 2025***. *"That's like when the exponential growth started, and then it kind of inflected with every model release. It started with Opus 4, then 4.5, then 4.6, now 4.7. It just kind of keeps inflecting."*
- **Pari pré-PMF assumé** : *"essentially we were trying to build this thing that was pre-PMF, and we knew that it wouldn't have PMF for 6 months because we were building for the next model."*

### "Coding is solved"

- Sondage à main levée :
  - *"Who writes 100% of their code by hand?"* → quelques-uns
  - *"Who writes 100% using an agent like Claude Code?"* → quelques-uns
  - *"Who's somewhere in between?"* → majorité (*"like 50% solved"*)
- **Cherny lui-même : 100%**.
- **Codebase Claude Code** :
  - *"It leaked, so people know."*
  - **TypeScript + React** — choisis car *"very on distribution for the model"* (le modèle de l'époque maîtrisait bien ces technos).
  - *"Pretty simple. There's nothing really complicated."*
  - **Modèle écrit 100% du code depuis octobre/novembre 2025**.
  - *"For me today, the model writes 100% of my code. I write somewhere usually a few dozen PRs every day."*
  - *"There was a day last week I did like 150 PRs in a day. That was a record."*
- **Limites assumées** : *"this is not the case everywhere. There's very big complicated codebases. There's weird languages the model isn't good at yet. Usually the answer is just wait for the next model."*

### Setup personnel actuel (mises à jour)

- **iOS first** : *"most of my work I do from my phone."*
- **App Claude → onglet code** : *"a little code tab on the left-hand side, I just have a bunch of sessions going."*
- **5-10 sessions** ouvertes, **"a few hundred agents"** actifs en journée, **"a few thousand"** la nuit pour deeper work.
- **Sub-agents** + **`/loop` slash command** = nouvelle primitive principale.
- ***"Loops are the future at this point. If you haven't experimented with it, highly highly recommend it."***

### Loop : la nouvelle primitive

- **Mécanisme** : *"You have Claude use cron to schedule a job for some point in the future, and it's a repeat job."*
- **Cadences** : every minute / every 5 minutes / every day — paramétrable.
- **Exemples Cherny** :
  - **PR babysitter** : *"fixing CI, auto-rebasing"*
  - **CI healthkeeper** : *"if there's a flaky test or whatever, it'll go and fix it"*
  - **Twitter feedback clusterer** : *"grabs feedback from Twitter and clusters it for me every 30 minutes"*
- **Routines** = équivalent serveur du loop : *"we just launched routines. Even if you close your laptop, it keeps going."*
- **4.7 démarre des loops spontanément** : *"I'll tell it 'pull this data query.' And it's like 'Hey, I noticed the data is changing over time. I'll start a loop and I'll give you a report every 30 minutes.' And I'm like 'Great. Can you send it to me over Slack?' And then it uses the Slack MCP to do that."*

### Vision sur les équipes

- *"There's going to be a lot more generalists than there are today."*
- Pas seulement *"product engineers cross-platform"* (iOS+web+server) mais ***cross-disciplinary generalists*** : *"engineers that are really good at product engineering, but also really great at design. Or really great at product and data science and engineering."*
- **Sur la team Claude Code** :
  - *"Every single person on our team writes code."*
  - Liste : engineering manager, PM, designers, data scientist, finance guy, user researcher.
  - *"They're specialist in something, but now also everyone's just coding."*

### Vision SaaS / disruption

- **Pas d'apocalypse SaaS**, mais **réordonnancement** via le framework **7 Powers de Hamilton Helmer**.
- **Powers qui deviennent moins importants** :
  - **Switching costs** — *"because you can just use the model and you can port from one thing to a different thing."*
  - **Process power** — *"Claude is getting really good at figuring out process. And especially with 4.7, it can just hill climb anything. So if you give it a target and you tell it to iterate until it's done, it will just do it. I think this is the first model like that."*
- **Powers qui restent importants** :
  - **Network effects**
  - **Scale economies**
  - **Cornered resources**
- **Prédiction startup** : *"the number of startups in the next 10 years that are just going to disrupt everything is going to increase like 10x."*
- **Pourquoi maintenant** : *"a tiny startup can build a thing that's as valuable as a large company and actually compete head-to-head, because the large company has to evolve their business process, retrain everyone, face internal resistance. But you, starting fresh, can build with AI natively 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."*

### Analogie pivot — Presse de Gutenberg

- **1400s Europe avant la presse** : *"essentially 10% of the European population was literate. They knew how to read and write. They were often employed by kings and lords that were not literate."*
- **50 ans après l'invention** : *"more literature published in Europe than in the thousand years before."*
- **Coût d'un livre** : ↓ **100×** sur la même période.
- **Quelques siècles plus tard** : *"literacy globally went up to like 70%. Now we can all read and write. You don't need a degree in reading and writing to know how to read and write. Although still there are professional writers."*
- **Analogie applicquée à 2026+** : *"software will be a thing that is fully democratized, that anyone can do. And it's going to be much faster than 50 years."*
- **Phrase-pivot mémorable** : *"The best person to write accounting software, I think maybe even today, is not an engineer, it's a really good accountant. Because they know the domain really well, and coding is the easy part. It's knowing the domain that's the hard part."*

### Modèle vs harness (Q&A)

- *"If you asked me a year ago, the ratio was maybe 50/50. If you asked me 6 months ago, would be 50/50. In 2 years? I don't know dude, we plan in like 1 week out."*
- **Le harness devient moins important** au fur et à mesure que le modèle s'améliore.
- **Évolutions du harness** :
  - Loops first-class
  - Easier to run lots of agents
  - Sub-agents (1 idée parmi d'autres)
  - *"There's a bunch more stuff that we're cooking."*
- **Dans 1 an** : *"the model will be much better aligned. And so all the safety mechanisms that we have today around prompt injection and static verification of commands and permission modes, human in the loop, all this kind of stuff is just going to be less important because the model will just do the right thing."*

### Démocratisation : tous codeurs comme on sait envoyer un SMS

- *"I think it's going to be a skill like — yeah, like I know how to send a text message."*
- Référence forte au modèle de la presse de Gutenberg ci-dessus.

### Pratiques internes Anthropic

- **Pas d'avantage modèle** : *"internally, we use the same models everyone else does."* Mythos pour test, beaucoup d'Opus 4.7 pour dogfood.
- **Pratique radicale** :
  - *"We use Claude for literally everything."*
  - *"Our Claudes are talking all day. As I'm coding, as my Claudes are coding in a loop, they will communicate over Slack to talk to other people's Claudes that are also running in a loop, to figure out unknowns."*
  - *"We have no more manually written code anywhere at the company."*
  - *"All of the SQL is written by models. Everything is just built by the models."*
- **L'avantage Anthropic n'est pas la techno mais le process** : *"the place that we're ahead is not the technology — same technology available to us is available to everyone here, because fundamentally we are building a platform. There's actually a far bigger lead in organizational structure and organizational process."*

### Multi-agent / parallélisation

- *"On the product side, it really just comes down to prompting. As the model gets better, it just naturally does this."*
- *"It's not on users to figure out how to hold the tools better. If that's the case, it's actually a product design problem and I'm not doing a good job."*

### Local vs cloud, computer use, MCP

- Local vs cloud : *"doesn't matter. By a couple years from now, the model is just going to be doing all the code. It's going to be starting the agents. It's going to be building the environments. If it decides 'actually I'll use local models to do this,' that's what it'll do. These I don't think these will be decisions that we are making as engineers anymore."*
- Knowledge work : *"largely, it's there already with Salesforce and Docs. For us, it's always just the simplest answer. It's MCP."*
- Computer use : *"I think currently, Anthropic is pretty far ahead on computer use. It's quite good. It's very slow, but it does it quite well now, especially with 4.7."*
- *"All this stuff just doesn't matter that much. It could be MCPs, APIs, just some sort of programmatic access — to the model, it's just tokens."*

### Produits à venir

- **Claude Design** : *"It's pretty good today. It's going to get a lot better."*
- **Claude Code** : *"There's also a few things that we're cooking up for Claude Code that are going to be landing over the coming weeks."*
- **Loop, batch, massive parallelism d'agents** : *"that's going to get better."*
- **Computer use**.

### Articulation dossier veille

- **Quatrième fiche Cherny** dans le dossier après :
  - **cherny-yc-lightcone-claude-code-origin-story-2026-02** (genèse YC Lightcone)
  - **cherny-claude-code-10-tips-team-x-2026-02-01** (10 conseils X)
  - **nunez-cherny-claude-code-workflow-venturebeat-2026-01-05** (workflow VentureBeat)
  - **wu-cherny-use-claude-code-builders-every-2025-10-29** (Wu/Cherny Every)
  - Plus la fiche **anthropic-claude-code-quality-postmortem-2026-04-23** dont Cherny est un des auteurs implicites.
- **Apport spécifique de cette fiche** vs les antérieures :
  - **Setup iOS exclusif** = nouveau (vs setup CLI/desktop des fiches précédentes).
  - **`/loop` + Routines** = nouvelle primitive d'architecture agentique présentée publiquement.
  - **Récit "Anthropic Labs incubator + Mike Krieger round 2"** = nouveau détail organisationnel.
  - **Inflection Opus 4 mai 2025** = datation précise du décollage.
  - **"100% code généré depuis octobre/novembre 2025"** = datation personnelle.
  - **Analogie Gutenberg** + **"the best accountant writes the best accounting software"** = phrases-pivots mémorables.
  - **"7 Powers" Helmer reordering** = analyse SaaS structurée.
  - **Sequoia / Lauren Reader** = nouveau support, public investisseurs.
- **Convergence majeure** :
  - **`/loop` agents en cron** = mise en pratique radicale du **Ralph Loop** (Trivedy 2026-03-10), du *Compound Engineering* d'Every (Shipper/Klaassen 2025-12-11), et du *Compounding Teams* (Schillace 2025-09-28).
  - **"Claudes talking to Claudes over Slack"** = mise en pratique des prédictions Levie *Building for Trillions of Agents* (2026-03-07) et de l'agent-native infra prônée par Karpathy (2026-04-29).
  - **"Coding is solved" + 100% code généré + 150 PRs/jour** rejoint **Curran/Intercom 3× R&D productivity** (2026-04-16, 93,6% PRs agent-driven), **Stripe Minions** (2026-02-09 et 2026-02-19), **StrongDM Software Factory** (2026-02-06).
  - **Démocratisation type Gutenberg** = même thèse que Karpathy (2026-04-29) sur les *neural computers* et que Andreessen sur la redéfinition du programmeur (2026-02). Aussi cohérent avec le projet "tout le monde peut coder" porté par Wescale (2026-05-03) et Habert PROJ-AI (2026-05-05).
  - **"7 Powers" et SaaS reordering** = pose un cadre **stratégie d'entreprise** rare dans le corpus 2026, complémentaire de Sun NYT *Permanent Underclass* (2026-04-30) côté économique et de Pawlowski *Tension Map* (2026-03-30) côté market research.
  - **"The harness becomes less important as the model gets better"** = nuance directe au courant *Harness Engineering* (Trivedy 2026-03-10, Osmani 2026-04-19, Böckeler 2026-04-02). Cherny anticipe l'absorption progressive du harness dans le modèle aligné.
  - **"Best accountant writes the best accounting software"** = corollaire de la *long-tail* de besoins métier que les fiches Wescale (2026-05-03 *"besoins historiques trop coûteux peuvent enfin être adressés"*) et Soto *Developer Taste* (2026-04) anticipaient.
- **Limites à signaler** :
  - **Optimisme techno-centric** assumé — Cherny est créateur Claude Code, biais d'évangéliste évident sur *"coding is solved"*.
  - **Pas de chiffres externes** — il s'appuie sur sa pratique personnelle et celle d'Anthropic. À comparer avec les chiffres rigoureux de Curran/Intercom (3× R&D, 93,6% PRs agent-driven).
  - **Sequoia format** : pas d'adversarial questioning, ambiance conviviale, pas de challenge sur la *jagged intelligence* (Karpathy 2026-04-29) ou sur la *permanent underclass* (Sun NYT 2026-04-30).
  - **"Coding is solved"** : déclaration provocatrice qui mérite d'être nuancée par Karpathy *"Opus 4.7 will simultaneously refactor a 100,000 line codebase and tell me to walk to a car wash 50 meters away"* (2026-04-29) — le coding *en surface* est en effet automatisable, mais le *jugement systémique* reste un domaine difficile.
- **À mobiliser pour** : présentation rétrospective 18 mois Claude Code (récit + datations) ; argumentaire startup *"best time to build"* en COMEX ; présentation *"loops as the future"* pour équipes ingénierie ; cours/conférence *"démocratisation du software par analogie Gutenberg"* ; débat sur la position du *harness* dans la doctrine 2026.

## RésuméDe400mots

Boris Cherny, créateur de Claude Code chez Anthropic, est interviewé lors d'un événement Sequoia par Lauren Reader. Sa thèse-déclaration centrale : ***"coding is solved"***. Lui-même n'a pas écrit une ligne de code en 2026 — le modèle écrit **100%** de son code depuis octobre 2025, *"a few dozen PRs/day, 150 PRs in a single day record"*.

Cherny raconte la **genèse de Claude Code** comme un récit pré-PMF assumé. Il rejoint **Anthropic Labs** (incubator interne) fin 2024, mission : explorer le *"product overhang"* — *"the model can do all the stuff that no product has yet captured."* À l'époque, le state-of-the-art coding était le *type ahead* (Sonnet 3.5). Pari : *"have the agent write all of the code."* Six mois où *"it just really didn't work. I used it for maybe 10% of my code."* Première release : *"it was not a hit."* **Inflection point : Opus 4 en mai 2025**, puis 4.5, 4.6, 4.7 — *"it just kind of keeps inflecting."* Round 2 de l'équipe maintenant dirigé par **Mike Krieger** (CPO Anthropic, ex-Instagram).

**Setup personnel actuel** : *"most of my work I do from my phone"* (iOS exclusif), 5-10 sessions, *"a few hundred agents going, a few thousand at night."* Nouvelle primitive : **`/loop`** — Claude utilise cron pour planifier des jobs récurrents (toutes les minutes, 5 minutes, jour). Exemples : PR babysitter (fixe CI, rebase auto), CI healthkeeper (corrige les flaky tests), Twitter clusterer (regroupe feedback toutes les 30 min). **Routines** = équivalent serveur, fonctionne laptop fermé. *"Loops are the future."*

**Vision SaaS** : pas d'apocalypse, mais réordonnancement via le framework **7 Powers de Hamilton Helmer**. *Switching costs* et *process power* deviennent **moins importants** (le modèle hill-climbe les processus avec 4.7) ; *network effects*, *scale economies*, *cornered resources* restent **inchangés**. Prédiction : ***"the number of startups disrupting in the next 10 years will increase 10×."*** Best time to build.

**Analogie pivot** : la **presse de Gutenberg**. 1400s Europe : 10% littéracie, scribes employés par rois illettrés. Cinquante ans après : plus de littérature publiée que dans les mille ans précédents, livre 100× moins cher. Quelques siècles plus tard : 70% littéracie. *"Software will be similarly democratized, but faster than 50 years."* Phrase-pivot : *"The best person to write accounting software is not an engineer, it's a really good accountant."*

**Pratique Anthropic** : *"We have no more manually written code anywhere at the company. Our Claudes are talking all day over Slack to other people's Claudes."* L'avantage Anthropic n'est pas technologique (mêmes modèles que tout le monde), mais **organisationnel**. À mesure que le modèle s'aligne, le **harness devient moins important** — prompt injection, permission modes, human-in-the-loop : *"all this kind of stuff is just going to be less important."* Produits à venir : Claude Design, loops/batch first-class, computer use.

## GrapheDeConnaissance

- Boris Cherny —a_créé→ Claude Code (TECHNOLOGIE, 0.99)
- Boris Cherny —affirme_que→ "coding is solved" (CITATION, 0.98)
- Boris Cherny —affirme_que→ il n'a pas écrit une seule ligne de code en 2026 (AFFIRMATION, 0.97)
- Boris Cherny —mesure→ 150 PRs en une journée (record) (MESURE, 0.97)
- Anthropic Labs —a_créé→ Claude Code, MCP, app desktop (TECHNOLOGIE, 0.97)
- Mike Krieger —dirige→ round 2 Anthropic Labs (ORGANISATION, 0.96)
- Opus 4 —permet→ exponential growth Claude Code en mai 2025 (EVENEMENT, 0.97)
- /loop —utilise→ cron pour repeat jobs (CONCEPT, 0.97)
- Boris Cherny —affirme_que→ "loops are the future" (CITATION, 0.96)
- Routines —est_variante_de→ /loop (équivalent serveur) (TECHNOLOGIE, 0.95)
- Hamilton Helmer —a_créé→ framework 7 Powers (METHODOLOGIE, 0.96)
- AI —réduit→ importance de switching costs et process power (CONCEPT, 0.94)
- Boris Cherny —affirme_que→ network effects, scale economies et cornered resources restent inchangés à l'ère IA (AFFIRMATION, 0.92)
- Boris Cherny —prédit→ 10× plus de startups disruptives dans 10 ans (AFFIRMATION, 0.93)
- Presse de Gutenberg —améliore→ littéracie en Europe (10% → 70%) (CONCEPT, 0.96)
- Boris Cherny —prédit→ le software sera démocratisé comme la littéracie post-Gutenberg, plus vite que 50 ans (AFFIRMATION, 0.93)
- Boris Cherny —affirme_que→ "We have no more manually written code anywhere at the company" (CITATION, 0.96)
- Claude agents —utilise→ Slack pour communiquer avec d'autres Claude agents (TECHNOLOGIE, 0.95)
- Boris Cherny —affirme_que→ l'avantage d'Anthropic est organisationnel et processuel, pas technologique (AFFIRMATION, 0.95)
- Modèle aligné —réduit→ importance du harness (prompt injection, permission modes, human-in-loop) (CONCEPT, 0.93)
- Boris Cherny —affirme_que→ "best person to write accounting software is an accountant" (CITATION, 0.96)
- Anthropic —publie→ Routines (server-side loops) (TECHNOLOGIE, 0.95)
- Claude Code —utilise→ TypeScript et React (TECHNOLOGIE, 0.97)
- Boris Cherny —utilise→ setup iOS-first multi-session multi-agent (METHODOLOGIE, 0.95)

---
Canonical: https://www.thekb.eu/en/fiches/cherny-sequoia-coding-is-solved-loops-printing-press-2026-05/