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.
Long-form article published on **September 14, 2026** on the X account **@GoogleCloudTech** (~2,000 words, four steps, six blocks of commands and configuration), signed by **Alan Blount**, Technical Solutions Consultant at Google. Starting point: a trivial question, handed to a research agent, billed at **$38**. The article proposes running **Claude Fable 5.1** and **Gemini 3.8 Flash** side by side behind the same **Gemini Enterprise Agent Platform** API (formerly Vertex AI). **(1) Configuration**: access to Fable is subject to Google Cloud's *Advanced AI Safety Addendum*, which requires a `setPublisherModelConfig` call with prompt-response sharing enabled for Anthropic, on pain of a 403; Flash works as soon as it is enabled. **(2) In-house benchmark** with promptfoo driving opencode on two tasks: on a git branch state, Flash answers in **1.1 s** for under a tenth of a cent while Fable costs **23 times more**; on a Postgres-to-Spanner migration, Fable produces in **12 s** a formal DAG with clock-drift risks and a rollback gate, whereas Flash delivers a linear sequence in 3 s. **(3) Usage**: *« asymmetric coordination »* — the fast model as first-line coordinator, the deep planner at checkpoints, an `ask_for_help` tool for escalation, and a warning against dynamic routers: *« Keep it boring »*. **(4) Token ROI**: the value of human time, shipped features, and incidents avoided, minus the cost of tokens and the team's ramp-up. The same task-boundary routing move as [[mazmanov-portal-spotify-shunt-claude-code-tokens-2026-09-03]], within the FinOps framework set out by [[rafal-wenvision-tokenomics-foundation-finops-ia-2026-06-04]].
#model routing#asymmetric coordination#tokenomics
Alan Blount (Technical Solutions Consultant, Google Cloud, @zeroasterisk) · publié sur le compte X @GoogleCloudTech.
*Deepdive* by **Gergely Orosz**, **Jessica Salmon**, and **Ivan Klaric** in *The Pragmatic Engineer*, published on **August 25, 2026**, based on interviews with Ramp's CTO **Rahul Sengottuvelu**, head of engineering **Hamid Dadkhah**, and **Zach Bruggeman**, founding engineer of **Inspect**. Paywalled article: the note covers the public portion (sections 1 through 3 and the opening of section 4; detailed architecture, sandbox internals, and collaboration remain behind the paywall).
**Zed** blog post signed by **Franciska Dethlefsen** (head of growth and marketing), published on **May 14, 2026** — the day after Anthropic's announcement — to answer Zed users' questions. **Subject**: starting **June 15**, Anthropic **splits Claude subscription billing into two pools** — one for its **first-party tools** (chat, the official Claude Code CLI), the other for **third-party agent and SDK usage** (anything going through **ACP**, `claude -p`, or a third-party tool). Usage via ACP **then stops drawing from the Pro or Max limits** and switches to a monthly **"Agent SDK" credit**: **$20 for Pro, $100 for Max 5x, $200 for Max 20x**. Once the credit is exhausted, usage continues **at standard API pricing** if overage is enabled — otherwise requests stop until the next cycle. **The figure driving the article**: subscriptions had until then subsidized agentic usage by a factor of **≈15 to 30×** relative to API pricing, and the new credits are billed **at full API rates** — hence *« for anyone using agents heavily, this is a major cost increase »*. **Three options are proposed**, in an order that reveals Zed's position: (1) keep the subscription by running the **official `claude` CLI in a terminal inside Zed** rather than via ACP — *« when the official claude CLI runs in the terminal, it uses your subscription's limits, not the new credit »*; (2) use Zed's built-in agent with the provider of one's choice (Zed-hosted models, API keys, Copilot, local Ollama, DeepSeek); (3) plug in **any ACP agent** — OpenCode, Codex, Factory, Cursor —, several of which still offer rate-limited subscriptions that subsidize heavy usage. **The underlying thesis**, and the real reason for the post: *« ACP is an open protocol… so that your editor is never locked into one provider's pricing decisions »*, with the explicit anticipation that *« this kind of change won't be the last »*. **The post carries an addendum dated June 16, 2026** announcing that **the change is suspended**: ACP, `claude -p`, the Agent SDK, and third-party applications continue to work with subscriptions **as before**, no separate credit to claim, limits unchanged, Anthropic revising its plan with advance notice announced. **The artifact is thus self-contradicting**: its most important content — the reversal — postdates its own publication date by a month.
#Zed#Anthropic#Claude subscription
**Franciska Dethlefsen** — head of growth and marketing chez **Zed Industries**. Le rôle est déterminant pour lire le texte : ce n'est pas un billet d'ingénierie mais une **communication de crise produit** · écrite le lendemain d'une annonce d'un fournisseur dont Zed dépend · à destination d'utilisateurs inquiets. La signature growth/marketing explique la structure (problème → options → réassurance) et le fait que l'argument protocolaire arrive en conclusion plutôt qu'en tête.