Engineering post by **Addy Osmani**, **Morgan Westlee Lunt**, and **Qing Wang** (the **Claude Code** team, **Anthropic**) on the *claude.dev* blog, published **October 15, 2026**; ~3,200 words. It describes the team's code review flow, in which Claude writes roughly **90%** of the code for Claude Code. From June to September, merged PRs **more than doubled** and the reverted share dropped by **more than 40%**; in Anthropic's monorepo, daily changes rose from **~2,500** (May) to **more than 30,000** (September).
#code review#code review#agentic code review
Addy Osmani · Morgan Westlee Lunt · Qing Wang — équipe Claude Code (Anthropic) ; blog *claude.dev* · catégorie Engineering.
A collective article by seven authors (**Zach Davis**, **Michelle Gill**, **Elisabeth Hendrickson**, **Angie Jones**, **Sha Ma**, **Randy Shoup**, **James Wickett**), published in the *Enterprise Technology Leadership Journal* by **IT Revolution** (fall 2026, vol. 3, no. 2), under a CC BY-NC-SA license. About **7,500 words**, titled *« Toward a Pattern Language for Code Reviews in the Age of Agentic AI »*. **(A)** Framing: code review is defined as an examination by a non-author entity leading to an action; empirical studies (Microsoft 2013, Mäntylä 2009, Beller 2014) show that its value lies mainly in maintainability and knowledge sharing, less in functional defect detection. **(B)** Three conditions for taking the human out of the critical path: maximal deterministic validation, **risk-graded** review, a **durable trace** of every agent decision; *« no human in the loop »* is a configuration choice, not a default. **(C)** Nine composable patterns, presented as a toolbox rather than a maturity ladder: small changes, Shift Left, design for verification, deterministic engineering practices, context engineering, continuous quality loop, adversarial LLM review, multi-agent reviews, specification-driven development. **(D)** Three case studies: **Block**, **Cloudflare** (131,246 reviews across 48,095 PRs in one month, 1.2 findings per review), **DryRun Security**. Extends the corpus's notes on context engineering and agent-assisted code review.
#agentic code review#code review#pattern language
Zach Davis (LaunchDarkly) · Michelle Gill (Engineered by AI) · Elisabeth Hendrickson (Curious Duck) · Angie Jones (Agentic AI Foundation) · Sha Ma (Topogy) · Randy Shoup (CircleCI) · James Wickett (DryRun Security) ; article collectif · IT Revolution.
Guide signed by **Michael Segner**, published on **August 20, 2026** on the claude.com blog in the *Claude Code* category: a **5-minute** read announced for approximately **31,500 characters** of body text, also offered as a PDF. Stated material: interviews with **more than a dozen** startups, fifteen named — **Artemis Security**, **Cainex**, **Clay**, **ClickHouse**, **Cognition**, **Commure**, **Crosby**, **Emergent**, **Harvey**, **Heidi**, **Higgsfield**, **Omni**, **Parahelp**, **Translucent**, **Zingage**. (A) Five operating rules: *everyone ships*, *automate the tedium*, *trust, but verify*, *build for rebuilding*, *prototype, dogfood, productionize*, each closed with product tips and gathered into a final checklist. (B) A body made of attributed quotes, each rule illustrated by named executives rather than by an aggregated metric. The four figures highlighted are those of the interviewed companies: **+30%** more features shipped (ClickHouse), **2 to 3×** engineering productivity (Omni), **100%** of bug triage automated (Clay), **more than 6,000 PRs per week** (Artemis Security). Two passages depart from the testimonial register: **Cainex**'s self-correction loop on medical coding, described step by step, and the internal use of **Claude Tag** at **Anthropic** as first responder for CI/CD on-call. The question posed at the opening — *"what would it look like if an organization built their product development lifecycle with Claude Code from the ground up?"* — connects with [[claxton-anthropic-ai-native-sdlc-playbook-2026-08-21]], published the next day by the same publisher, and extends [[cherny-wu-reflecting-year-claude-code-2026-07-17]].
#Claude Code#startups#everyone ships
Michael Segner · auteur du guide sur le blog claude.com (fonction non affichée par la page) ; entretiens avec les dirigeants de quinze entreprises nommées.
Issue of the **Engineering Enablement** newsletter from **DX** signed by **Brian Houck**, published on **August 5, 2026**, approximately **13,000 characters**. The text opens with a quantified observation: at **Meta**, significant lines per diff merged by a human increased by **106%** in one year and diffs per developer per month by **51%**, with more than **80%** of this growth coming from agentic AI, while the share of diffs reviewed within 24 hours declines; DX's analysis for its part measures a median pull request size up **64%**, while developers want to devote about **7%** of their time to review. (A) Before handing review over to AI, Houck reframes the usage question: *"What problem was code review solving before AI arrived?"* If the answer is defect detection, full automation becomes inevitable; the **Bacchelli & Bird** study (*Modern Code Review*, ICSE 2013) shows that defect-related comments account for only **14%** of comments actually written. (B) Part of the burden is *self-inflicted*: the 2016 Microsoft study of **911 developers** already identified turnaround time, review size, and understanding the motivation for the change as the top three obstacles, and only **26%** still wrote a detailed description. (1) **RADAR** at Meta serves as the reference deployment for risk stratification. (2) Three ordered moves: fix the fundamentals, design AI around human judgment, protect what review invisibly produces. The corpus already includes [[monperrus-end-of-code-review-agents-supersede-2026-06-11]], which pushes automation to the point of replacement, and [[laycock-thoughtworks-reviewing-all-this-code-2026-09-02]], the direct response to this text.
#code review#code review#review queue
Brian Houck · signataire de l'édition · sur la newsletter Engineering Enablement de DX ; fonction non affichée par la page.
An arXiv paper (cs.SE) by Martin Monperrus arguing a radical thesis for the SDLC: coding agents have crossed a threshold of capability such that **human code review is no longer a necessary component** of a quality pipeline. Two claims: (1) autonomous LLM-based systems achieve all the goals of review (defect detection, quality, compliance) at lower cost and higher throughput; (2) the hybrid model "the agent writes, the human reviews" is untenable — it does not ensure real quality and does not scale with AI velocity, creating a "false sense of security". Monperrus contrasts inspection de Fagan (1976) with a **multi-agent adversarial verification pipeline** (generator agent + independent reviewer agents + tests/formal methods + vote-based consensus). The human refocuses on the spec, architectural trade-offs, approval of critical domains, and edge cases. Recommendations: pilot first on low-risk components, measure agent vs. human, make rejection decisions explicit.
Manifesto-style article by **Thariq Shihipar** (Engineer & serial entrepreneur, Claude Code team at Anthropic) announcing a **change in the default output format for agents**: replacing **Markdown with HTML**. Thesis: Markdown has been the dominant format between humans and agents (simple, portable, editable, readable) but has become **a bottleneck** as agents produce longer and richer artifacts (specs, plans, reports, code review). Beyond ~100 lines, no one reads a Markdown file anymore. HTML solves six limitations simultaneously: **information density** (tables, CSS, SVG, scripts, canvas, images), **visual clarity** (navigable, mobile-responsive layout), **ease of sharing** (an S3 link directly openable in a browser), **two-way interactivity** (sliders, knobs, "copy as JSON/prompt" buttons to loop back into Claude Code), **native contextual ingestion** (Claude Code reads the codebase + MCP Slack/Linear + git history + Chrome) and **enjoyment** (the author explicitly claims *"it's joyful"*). Five canonical uses detailed: (1) **specs/plans/exploration** in a comparative grid, (2) **PR review** with inline annotated diff, (3) **design & prototypes** with animation sliders, (4) **reports/research/learning** (the author had a prompt-caching explainer generated from git history), (5) **custom throwaway editors** (drag-and-drop of Linear tickets, feature-flag editors, side-by-side prompt-tuner) that produce a re-injectable "copy as markdown/diff/JSON" export. Explicit anti-pattern: *"I'm a little bit afraid that people will read this article and turn it into a /html skill"* — the author **rejects premature skill-ification**, recommending prompting from scratch ("make a HTML file"). Pragmatic FAQ: token cost absorbed by **Opus 4.7**'s 1MM context, 2-4× longer generation, noisy HTML diffs (a real downside), style kept in check via a reference HTML design system.
#HTML#Markdown#output format
Thariq Shihipar (Engineer & serial entrepreneur, équipe Claude Code chez Anthropic — site : thariqs.github.io/html-effectiveness ; X : @trq212)
Cat Wu and Boris Cherny (Anthropic) explain how to use Claude Code like its creators: antfooding, plan mode, subagents, hooks, and extensibility — Every's AI & I podcast
#Claude Code#Cat Wu#Boris Cherny
Rhea Purohit (interviewer: Dan Shipper) · Cat Wu · Boris Cherny