Skip to content

root / tags / ingenierie-de-contexte

#ingénierie de contexte

5 fiches

Quality & Security Auto-verified translation

Agentic AI and Code Reviews: Toward a Pattern Language for Code Reviews in the Age of Agentic AI

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.

AI Coding Agents & Skills Auto-verified translation

Stop Running the SDLC on Models That Aren't Human

Chris Williams (@voodootikigod) opens his ADLC series arguing that running the human SDLC on models is a category error: the classic cycle was designed to counter human failure modes (ego, fatigue, forgetting) that are absent in LLMs. He catalogs eight load-bearing failure modes (F1-F8) and five exploitable properties (E1-E5), and lays out the founding principle: every phase of an agentic cycle must trace back to a failure mode it defends against or a property it exploits.

#ADLC#agentic development lifecycle#SDLC

Chris Williams (@voodootikigod)

AI Coding Agents & Skills Auto-verified translation

Two Human Gates and Everything Between Is Machine-Checked

Second installment of Chris Williams's ADLC series: it unrolls the cycle that follows from the "first law" — eight phases (P0 Triage → P7 Distill), a deterministic gate between each pair, and exactly two mandatory human moments (spec approval at P1, behavioral acceptance at P6). Key principle: an LLM→LLM handoff without a deterministic checkpoint multiplies error rates; and a "barbell" cost distribution (heavy at both ends, light in the middle) that inverts agile economics.

#ADLC#eight-phase agentic cycle#deterministic gates

Chris Williams (@voodootikigod)