How teams and organizations adopt AI-assisted development.
83 fiches · 167 entities · Updated
Moving from experimenting with AI-assisted development to depending on it is a process, and this collection follows it. Engineering cultures absorb coding agents unevenly; roles and workflows shift; resistance and rework surface; productivity claims meet real constraints. Fiches gathered here report on organizational change, skills transfer, and the measured effects of AI on how software teams work day to day. Benchmarks of developer output, and the arguments over how to read them, run throughout. What draws attention is lived transformation — the pilots, the rollouts, the distance between a promised gain and a realized one — with the tools themselves left to other collections.
Key figures
0.31 SD overall improvement
Programme de tutorat IA · stated in source
14% des AI-using workers expérimentent du brain fry
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.
Corporate blog post from **Block** (`block.xyz/inside`), unsigned — the displayed author is **"Block"** —, published on **August 18, 2026**, ~930 words, announcing **the open-sourcing of Berd**, Block's internal desktop application for working with agents, and laying out the design thesis that guided it: giving agents character *"not only through roles, instructions, skills, and tools, but through distinctive visual identities"* — hence the in-house animated characters, the *"Gloopies"*. The post starts from an observation of fragmentation (*"The technology was powerful, but the experience around it was fragmented"*) and a precisely named interface problem: *"the product gives people little sense of how the agent is configured, which context and tools are available to it, and how it differs from another agent"*. Two structuring contributions. **(A) A three-tier articulation**: **goose** remains the framework and *runtime* that holds the agent loop; **Berd** is the desktop client (projects, context, sessions, agents, configuration); the two communicate via the **Agent Client Protocol**. **Buzz** is designated as the follow-up, for when solo work becomes collaborative (*"Start alone, then go multiplayer"*). **(B) Six requirements handed off to Buzz**, stated as a takeaway: *"private space, durable context, recognizable agent identities, reusable skills, visible configuration, and clearer visibility into an agent's configured context, tools, and capabilities"* — a grid directly reusable for evaluating an agent client. The text itself distinguishes identity from capability: *"The avatars make the agent recognizable. Its role, skills, and tools make it useful."* No usage figures are produced and no license is named for the open-sourcing.
#Berd#Block#open source
**Aucun auteur nommé** : le billet est signé **« Block »** — le champ *Author* de la page porte le nom de l'entreprise. Publié le **18 août 2026** sur `block.xyz/inside` · le blog **corporate** · et non sur `engineering.block.xyz`.
X post by **Andrew Ng** from **August 14, 2026** (16:29 UTC), reprising the "Dear friends" letter from ***The Batch* #366** (DeepLearning.AI, same date), ~900 words. Ng presents **The AI Engineering Skills Map** and publishes **four skills** held to be the most important. **(1) Building and deploying AI applications** — the specificity is named: *« The key difference between AI and non-AI applications is that the former has unpredictable outputs »*, hence the emphasis on *evals* and error-analysis loops. **(2) Software engineering fundamentals**, because *« Understanding software fundamentals allows you to recognize what tradeoffs even exist »* — the inexperienced developer fails *« because they don't know what context to give their coding agent »*, hence the goal of *« steering coding agents using the precise language of software engineering »*. **(3) Using coding agents**, in an operational formulation: *« help the agent autonomously close loops by providing verifiers or evals »*, and *« knowing how much to intervene and how much to leave them alone »*. **(4) *Shaping the build***: *« Given a clear spec, coding agents are rapidly improving at delivering to it. Thus, our work as engineers is shifting toward deciding what should be in the spec »*, paired with *« Engineers should no longer expect to be given a pixel-perfect design and asked only to implement it. »* A **terminology note** carries most of the framing: Ng talks about **skills** in AI engineering and **not the role** "AI Engineer", with an explicit analogy — *« All developers today should know how to work with the cloud, and only a smaller number have a "Cloud engineer" title. »* The whole is backed by *« an analysis of more than 10,000 job postings, dozens of structured interviews with experts, hiring managers, and recruiters, surveys, and other online data »*, of which **no numeric results are published**: Ng describes his process as *« informally… akin to running clustering »* and announces a detailed map in future posts. He states the interest in the second-to-last sentence: *« DeepLearning.AI's principal focus is to help developers gain these AI engineering skills. »*
#AI Engineering Skills Map#skills map#Andrew Ng
**Andrew Ng** — fondateur de **DeepLearning.AI** · general partner d'**AI Fund** · cofondateur de **Coursera** et de **Google Brain** · ancien chief scientist de Baidu. Texte signé · à la première personne · écrit *« with my team »* sans qu'aucun collaborateur soit nommé. Publié le **14 août 2026** sur X et dans ***The Batch* n°366** — même texte aux deux endroits ; préférer *The Batch* pour toute citation durable. Quatrième fiche Ng du corpus · après les lettres n°350 (24 avril) · n°352 (8 mai) et n°359 (26 juin).
Internal research report dated **August 12, 2026** (in *What? — So What? — Now What?* format, investigation conducted August 11-12) on a simple question: are the **desktop** applications of ChatGPT and Claude better than their **web** versions? The answer comes in two parts. **(A) A solid, well-sourced qualitative consensus exists.** The starting point is indisputable: desktop and web call exactly the same cloud models, the application being merely an interface to the service — the gain therefore lies entirely in the application shell (access latency, stability during long sessions, memory footprint, system integrations, workflow fluidity). What genuinely distinguishes desktop, confirmed: on the OpenAI side, a global shortcut (Option/Alt + Space), a *companion window* that always stays on top, native screenshots, and since July 2026 the **Codex/Work** agentic capability built into the app; on the Anthropic side, **Quick Entry** (macOS), **Desktop Extensions** (installing a local **MCP** server becomes *"as simple as clicking a button"*), access to local files, **Cowork** and **Computer Use** (Accessibility permissions and screen recording). The web retains two confirmed strengths: multiple tabs/threads, and universality without a client to install. **(B) Nearly all the figures circulating to support this consensus do not withstand verification.** The report's critical audit (§1.5) classifies **unconfirmed** seven widely repeated numerical claims: the *cold start* "2-3 s vs 8-12 s" (the only trace being an anecdotal *"loads in about 3 seconds"* on Substack); RAM usage "200-700 MB vs 1.2-2 GB," attributed to an "Alibaba Product Insights" whose pages return **404**; an untraceable glitch rate and session retention figure; a "Claude +10-20% end-to-end" attributed to **Skywork**, which had in fact benchmarked its own Windows agent rather than Claude against the web; an untraceable "Cosmo Edge" source; unconfirmed Zenken AI citations; and two unauthenticated X posts with no URL. The counter-signal is documented with the same rigor: Yuri Dvoinos describes a Claude Desktop app that *"makes me want to throw my laptop out the window"* — 68% CPU usage, input lag on a MacBook Pro — and the report notes that both apps are **Electron** builds with native layers. Hence its formulation: *the desktop advantage is a promise of implementation, not a law of nature.* **The "So What"**: since the model has become the common denominator, the interface becomes the battleground — the **Codex + ChatGPT** merger of July 9, 2026 and the Cowork/Computer Use tandem tell the same story, *"the desktop app is no longer a chat client, it's an agent runtime with access to the machine."* Three consequences: the gain is a **friction** gain, not a power gain; for a CIO, desktop **shifts the trust boundary** — Computer Use requires sensitive system permissions and the Codex merger places code execution, browser, and connectors within *"one expanded trust boundary,"* whereas the browser remains governable via SSO, DLP, and CASB; and for anyone publishing, the fragility of the figures is itself the story. **The "Now What"** delivers individual switching criteria, a CIO checklist (inventory permissions, disable Computer Use and Cowork by default, scope which MCP extensions are authorized, organize distribution and updates — on Linux, outside the apt repository, Claude Desktop does not update itself) and an editorial directive: cite only confirmed verbatims and dates.
#ChatGPT Desktop#Claude Desktop#web version
**Deep Research Veille Interne** — rapport non signé · produit par une enquête sourcée menée les **11-12 août 2026** et rendu le 12.
Experience report published on **LinkedIn Pulse** on **August 12, 2026** by **Guillaume Dumortier**, in his newsletter *Growth Marketing Fit*, subtitled *« Four layers, a lot of rebuilding, and the failure modes nobody warns you about »*, ~2,500 words. The subject: an internal AI system built **in Claude** for a marketing team of about sixty people — roughly thirty content and sales **skills**, a dozen **source-of-truth modules**, **seven agents, six of which exist only to check work rather than produce it**, a **plugin** for those who live in a terminal, a **browser application** carrying the same knowledge for everyone else, and an orchestration that chains three or four assets into a *campaign bundle*. The thesis is set out early: the quality of an AI output is not determined at the moment of generation, but by what the system knows before it starts and by what happens to the draft afterward — *« The generation step in the middle is the easy part. It's also the only part most teams have built. »* Hence four layers: **Truth** (almost nobody builds it), **Production** (everybody), **Verification** (almost nobody), **Internal distribution** (*« where good systems die of neglect »*). Two failure mechanisms carry the article. **(A) The verifier's bare closed-world « pass »**: a fact-checker backed by product documentation receives a draft containing a claim about another product, one its sources did not cover — it returns a *« pass »*, not because the claim was true but because nothing contradicted it. *« It didn't just miss the error, it certified it. »* Fix: forbid a bare verdict and require every report to declare its **own coverage** — how many claims were checked, how many matched to sources, which fell outside its jurisdiction, which were owned by no source. *« "I can't verify this" became a first-class result. »* **(B) The cross-asset contradiction**: two assets can each be individually correct, each traceable to a real source, and still contradict each other — the press release states one date, the blog post another, both pass, the bundle can't ship. *« Per-asset verification can't catch that, by construction. »* Article's closing clause: *« The generation is free. The trust is the product. »*
**Guillaume Dumortier** — auteur de la newsletter LinkedIn **Growth Marketing Fit** (~1 300 abonnés à la publication). Il écrit en **praticien-constructeur** : il a passé *« une longue partie de cette année »* à bâtir et exploiter le système décrit. La légende de l'illustration précise le socle technique — *« A custom-built Marketing AI OS within Claude »*. Publié le **12 août 2026**.
Long-form article published on **X** on **August 11, 2026** by **Jesse Zhang**, CEO of **Decagon** (customer-service AI agents), under a dilemma-shaped title — *« To FDE, or not to FDE? »* — devoted to the **Forward Deployed Engineer**, which has become *« the answer to almost every hard question in AI go-to-market »*. Starting observation: Anthropic and OpenAI have built enterprise deployment arms explicitly modeled on Palantir, *« every seed-stage company »* advertises an FDE offering, and job postings for the title are said to be up several hundred percent in a year. **(A) The Palantir genealogy** supplies the framework: **Shyam Sankar**'s (CTO) formula, *« FDEs eat pain and excrete product »*, and **Joe Lonsdale**'s reminder that Palantir spent nearly two decades being called a *« glorified consultancy »* on the basis of an accurate observation. **Gotham**'s bespoke deployments (CIA, NSA, military intelligence) were encoded into platform primitives — ontology, object models, permissions, workflow engines, provenance tracing — which became **Foundry**, then Apollo and AIP; standardization pushed gross margin into the 80% range and Palantir moved from an FDE motion to account-based selling, with many FDEs migrating into core engineering. *« The pain was the input to the product, not a cost of sale. »* **(B) The criterion proposed** is not to give up on FDEs but to know when to stop: go early, then ask whether one is still **discovering** — *« The trap is not starting. It's not stopping. »* **(C) A distinction few make: FDE ≠ implementation.** *« Building that integration into their ticketing system »* is real work, but it is execution against a known spec, not discovery of an unknown one; conflating the two *« is how a company convinces itself that a growing services org is a product investment »*. Closing line: *« If your FDEs are eating pain and excreting more pain, you don't have an FDE team. You have a services business. »* Two figures are put forward about Decagon — *« two-thirds of deployment work is now done autonomously via Duet »* and *« a few days on average to launch the first AOP, even for large banks, airlines, telcos »* — without the "deployment work" denominator being defined or the AOP acronym spelled out.
#Forward Deployed Engineer#FDE#engineer embedded with the client
**Jesse Zhang** — cofondateur et **CEO de Decagon** (agents IA de service client, San Francisco) · 85 000 abonnés sur X · site personnel `jessezhang.org`. Il cite son cofondateur **Ashwin Sreenivas** · **ex-Palantir** · d'où la profondeur du récit Palantir. Publié le **11 août 2026**.
Trade-press brief (**Payments Dive**, *Dive Brief* format, **August 6, 2026**) covering **Block**'s quarterly earnings release: the company has already rolled out several AI tools to its customers — **Moneybot** (Cash App) and **Managerbot** (Square) — and has not yet decided how to charge for them. **Jack Dorsey** on the analyst call: *"We're in a fortunate position where we can experiment with a number of models, and then choose the right one that's going to align all of our incentives with our customers."* **The financial backdrop illuminates that stance.** Six months earlier, Block had laid off roughly **4,000 people, about 40% of its workforce**, in a reorganization explicitly framed around AI. In Q2 2026: gross profit **up 25% to $3.2B**, revenue **up 10% to $6.62B**, but **net income at $89M, down 83%** year over year due to severance costs closing out the restructuring; 2026 guidance was raised. AI's value, then, is being captured through the cost structure before it is captured through price. **The heaviest fact sits in the middle of the brief**, drawn from the shareholder letter: *"Starting in June, agentic AI helped write and review nearly all of our production code changes"* — writing **and** reviewing nearly all production code changes, at a publicly traded payments company, six months after cutting 40% of the workforce. A self-reported claim to investors, with no definition of *"nearly all"* or of what *"review"* covers. **The tooling**: **Goose**, an internal system built two years earlier, described as model-agnostic (it plugs in different commercial models for employees); **Buzz**, launched the previous month for *"agent collaboration, communication, and code repositories."* **On the customer side**: Moneybot monitors Cash App user activity and surfaces accounts, balances, and transactions — over **one million weekly active accounts**; Managerbot runs automated marketing, margin analysis, and suggests *"operational fixes"* to Square merchants. **Evercore ISI** analysts list four monetization paths — SaaS bundles, direct subscriptions, enterprise offerings, usage-based pricing — **none of them tied to outcomes**. Stated order of priority: **product quality → distribution → adoption → pricing model**. Two distribution facts round out the picture: Square is rolling into **Google Maps** with a *"conversational AI experience,"* described as *"the first step in a broader partnership between Square and Google"*; and the **Tags** payment device (keychain and NFC chip wands) shows **three million people on the waitlist**. Analyst quotes: William Blair (*"Block epitomizes the secular shift toward tech-forward digital finance firms"*) and Bank of America on the *"post-reset operating model."*
#Block#Jack Dorsey#Cash App
**Justin Bachman** — Senior Reporter · **Payments Dive** (groupe Industry Dive). Journaliste sectoriel paiements ; signe ici un **Dive Brief** · format court en deux temps (*Dive Brief* = les faits du jour, *Dive Insight* = le contexte) qui compile une conférence de résultats · une lettre aux actionnaires · un communiqué et trois notes d'analystes.
In-depth op-ed published on **sfeir.com** on August 1, 2026, authored by **SFEIR** (the firm's editorial voice). It brings together **two July 2026 publications** with opposite methodologies — the preregistered field experiment **"The Cybernetic Teammate"** at **Procter & Gamble** (Dell'Acqua, Ayoubi, Lifshitz, Sadun, **Ethan Mollick** et al., *Organization Science* 37(4), 2026) and the first report in **OpenAI Economic Research**'s **"Work at the Frontier"** series (Jul. 27, 2026, >800,000 messages from US ChatGPT users) — into a single thesis: *"generative AI doesn't just speed up existing work, it redistributes who does what."* The architecture unfolds in four stages: **the mechanism** (P&G: AI acts as a *boundary-spanning* device, erasing functional silos — an individual + AI reaches the level of a pair without AI, **+0.37 σ**), **the scale** (OpenAI: **43.5%** of profession-specific messages fall outside the user's own profession), **the agenda** (Mollick: the walls are thinning, the division of labor must be rethought, and well-orchestrated recomposition "pays off handsomely"), then **the firm's response** — **Skill Based Organisation (SBO)**, adopted at SFEIR under the impetus of **Rosalie Zandona** (VP People & Culture): **actually operational skill** replaces the job description as the unit of organization (**up to 13 skills identified per role**), shifting from a **status-based identity** ("I am a manager") to an **operational identity** ("I know how to design complex architectures"). The rhetorical move is proof by internal example: *"we made the shift in-house before recommending it."* **Three caveats are noted**: the SBO shift dates back to **February 2026**, hence *predating* the diagnosis it is supposed to resolve (the argumentative order reverses the chronological order); **nothing in the data demonstrates** that a skill-based organization absorbs crossover better than a role-based one (an untested design hypothesis); the P&G result has been circulating **since March 2025** (NBER w33641) — the "a few weeks earlier" applies to the peer-reviewed publication, not to the result itself.
#Skill Based Organisation#SBO#skill-based organization
**SFEIR** — ESN française « AI Only » (~850 ingénieurs, 8 agences France & Benelux). Voix éditoriale du cabinet (byline « SFEIR »).
Post and report from **OpenAI Economic Research** published on **July 27, 2026**, the first installment in the **Work at the Frontier** series, analyzing **more than 800,000 messages from US ChatGPT users**. **Coined concept**: ***task crossover*** — *« work historically associated with one occupation appearing in the AI use of people in another »*. **The headline figure is actually two figures, and that's the point coverage loses**: **16.8% of work-related messages** concern tasks associated with another occupation, and **43.5% of occupation-specific messages**. The funnel explains the gap: **61.5% of usage is generic** (writing, summarizing, planning — too widely shared to count as evidence of crossover) and is excluded; of the **remaining 38.5%**, **43.5% fall outside the occupation** and 56.5% are *« inside **or near** »* — so the upper bound is calculated on a reduced base, while the lower bound is calculated on the entire professional usage. **By occupation** (share of occupation-specific messages pointing to an external task): customer experience **77%**, design **75%**, HR **69%**, legal **56%**, marketing **53%**, sales **40%**, finance **40%**, engineering **28%** — *« a majority in five of eight groups »*. **Two distinct directions of circulation**: design **imports** (35.2%) and **exports** almost nothing (1.7%); engineering does the opposite (imports 18.5%, exports 7.4%); **marketing does both** (imports 24.3%, exports **8.9%**, the highest outward share in the sample). **Two tasks appear in the top 3 of borrowings for the other seven groups**: **financial calculation** and **technology troubleshooting**. **The heatmap, absent from coverage, is the richest object**: it gives the full distribution of tasks by user occupation, and its diagonal is striking — engineering retains **53%** of its own work while customer experience retains only **11%**, HR **10%** and design **12%**. **Size effect**: the outside-occupation share drops from **18.9%** (2-5 employees) to **16.3%** (>100 employees) — **but only « among average users »**, OpenAI specifying that *« among the heaviest users, we do not see the same monotonic pattern »*, and concluding conditionally: *« AI **may be** especially useful as a generalist tool where specialist resources are scarce. »* **Claimed status**: an **early signal**, visible *« before firms rewrite job descriptions or create new job titles »*. **Structural caveat**: OpenAI measures OpenAI's own usage, on US ChatGPT users only, and presents this position as an asset — *« our unique window into how the world of work is changing »*.
#OpenAI Economic Research#Work at the Frontier#task crossover
**OpenAI Economic Research** — équipe de recherche économique d'OpenAI ; la page crédite simplement *« OpenAI »* et la classe sous les tags *Economic Research* et *2026*. Le billet est la porte d'entrée d'un **rapport PDF** (`work-at-the-frontier-report.pdf`) et s'adosse à un cadre antérieur de la même équipe · l'**AI Jobs Transition Framework** · dont il reprend la thèse que de nombreux métiers vont **se réorganiser** plutôt que disparaître.
Capgemini (Aiman Ezzat, CEO) — Investir interview, "boss special": IA agentique as an operational breakthrough, not just another technology; €2bn invested, +30% on application development and −20% incidents, >11% of Q1 bookings, TAM of over $400bn/year by 2030 — but "very far from plug and play" (Investir / Les Echos)
#Aiman Ezzat#Capgemini#IA agentique
Aiman Ezzat (directeur général de Capgemini) · propos recueillis par La Rédaction d'Investir
In-depth opinion piece published on **sfeir.com** on July 23, 2026, signed by **SFEIR** (the firm's editorial voice). It is a **strategic commentary on Trésor-Éco note No. 391** from the DG Trésor (June 2026 — see [[dgtresor-ia-effets-emploi-2026-06-30]]), read through SFEIR's doctrine of « **amplifying AI rather than enduring it** ». The article praises Bercy's **cautious economist's tone** (mechanisms plus uncertainty rather than a prediction) and draws from it a **three-part thesis**: (1) **no measurable aggregate effect** at this stage (two offsetting forces — displacement vs. productivity — EU adoption ~20%); (2) a **single solid empirical signal, on juniors** (−16% employment among exposed 22-25 year-olds in the US); (3) a **long-term danger that shifts the question** — **competitive lag** (non-adoption), not job destruction. The analytical core SFEIR retains: **price elasticity** determines the employment effect (the **Jevons** paradox applied to code) → the argument is **structurally pro-employment for developers**. The article **dismantles the "AI layoffs" narrative** (4.5-6.2% of US layoff announcements, "labeling" at 59%) and points to the note's **blind spots** (the agentic scenario relegated to a footnote; diffusion speed not discussed; OpenAI/Anthropic having become sources for Bercy = an unflagged source bias). **SFEIR's operational translation** (for CIOs/CTOs): value migrates toward intent/architecture/control, training **augmented engineers** (**AI Champions** programs), and avoiding rushed adoption (**workslop**, technical debt) through **context engineering** and governance.
#AI and employment#competitive lag#non-adoption
**SFEIR** — ESN française « AI Only » (~850 ingénieurs, 8 agences France & Benelux). Voix éditoriale du cabinet (byline « SFEIR »). Positionnement de la maison sur la transformation IA des DSI ; ce texte prolonge la ligne éditoriale portée notamment par Didier Girard (cf. [[girard-sfeir-ai4it-vs-ai4business-budgets-2027-2026-06-24]]).
SFEIR analysis (consulting-firm voice, "an engineer's reading") articulating two frameworks too often conflated: the **SDLC** (Software Development Life Cycle — *building the software correctly and reliably*) and the **PDLC** (Product Development Life Cycle — *building the right product and succeeding in the market*). Central thesis: the two cycles are not competitors but **nested** — the SDLC is the subset of the PDLC **housed under its development phase**; when a product team reaches the "build" stage, a full SDLC cycle (design → build → test → review → deployment) runs inside it. The SDLC is standardized (**ISO/IEC/IEEE 12207**, 2017 and 2026 editions), with its lineage of models (Waterfall 1970, V-model, iterative/spiral, **Agile 2001**, **DevOps/DevSecOps 2009+**) and its **DORA** metrics (throughput, stability, MTTR, change failure rate). The PDLC, being the umbrella cycle, runs from **ideation/discovery** to **market withdrawal** (not to be confused with the marketing **PLC** of Theodore Levitt, 1965, which describes a *commercial curve*, not *organized work*: "the PLC observes a curve; the PDLC organizes work"). **Tipping point**: the SDLC natively addresses **only one risk in four** — via **Marty Cagan's "Four Big Risks"** framework (Value → PM, Usability → Designer, Feasibility → Lead Engineer, Business viability → PM) — an organization excellent at SDLC but blind to PDLC produces "software nobody wants" — John Cutler's **"feature factory"** (success measured by output, not outcome). **Why AI changes everything**: generative AI **compresses the SDLC** (Google/JetBrains data, May 2026: **~85% of developers** regularly use coding agents, **~41% of new code** is AI-generated; implementation goes from weeks to hours), so the **bottleneck shifts upstream** — deciding *what* to build (Marty Cagan, April 2026: "when the cost of delivery collapses, the bottleneck shifts to discovery"). Consequences: DORA 2025 (~5,000 professionals, 90% AI adoption) shows a **positive correlation with throughput but a negative one with stability** (more unvalidated features means instability and rework); Andrew Ng (AI Startup School, July 2025) reports teams **reversing the "1 PM for 4 engineers" ratio to "2 PMs for 1 engineer"**; and with **spec-driven development**, the PDLC/SDLC boundary becomes **porous** (the product spec becomes directly executable by agents). **What a CIO should take away**: an augmented SDLC becomes a **market standard, not a differentiator** — the junction with the product must be instrumented, **executable specifications** demanded as input, technical metrics cross-referenced with outcome metrics, and the role of "feature supplier" **refused**. For a CPO: the shift of the bottleneck toward discovery is both a **promotion** (product judgment becomes scarce again) and a **notice to act** (industrialize discovery to reach parity with the SDLC). SFEIR's in-house framework ("Designing and building in the agentic era" — **11-phase cycle** + **Software Factory 10x**) is positioned as the answer on the engineering side, with the **articulation of the two cycles** as the next lever. Conclusion: "as code becomes a commodity, margin shifts toward product judgment and governance."
Boris Cherny (Head of Claude Code) and Cat Wu (Head of Product, Claude Code) publish a short LinkedIn video, "Reflecting on a year of Claude Code," in which they put forward a thesis: **product and engineering roles are merging**. At Anthropic, the product team, devrel, and design **all write code**; many engineers **ship products end to end** (idea → build → legal/marketing/security → release into the world). Their conclusion: AI benefits profiles with **curiosity**, **product taste**, and a taste for **end-to-end ownership**. The note mainly captures the **comment-thread discussion** (55 comments, 28 substantive): a consensus that **reframes** the thesis — it is not roles disappearing, it is that **shipping becomes cheap**, which shifts value toward judgment and defining the right problem — set against a lucid minority on the flip side (accountability, governance, IP).
#Boris Cherny#Cat Wu#Claude Code
Boris Cherny (Head of Claude Code, Anthropic) et Cat Wu (Head of Product, Claude Code, Anthropic) — vidéo ~47 s publiée par Claude for Business sur LinkedIn · repartagée par Claude. Commentateurs cités : Omer K. · Syed T. · Andrei K. van Noordt · Kristóf Nagy · Natasha Egan · Natasha Newbold · Rehan Nazir · Noman A. · Kevin Schoovaerts · Sunny Vara · Paul Breuler · Ron H. · Mohammadjavad Sayadi · Chris Bounds · Mohamed Anis · Panny Malialis · David H. · plebs.me · James Hutchinson · Dewayne J Grunden II · e.a. (28 commentaires de fond retenus sur 55).
**Boris Cherny** (Creator & Head of Claude Code @Anthropic) publishes a framework table on LinkedIn, **« Steps of AI Adoption »**, mapping an engineering team's adoption of agentic AI across **5 stages (0→4)**, each characterized by an **order of magnitude of agents driven** and a **transformation of the engineer's role**: **0 Gated** (0 agents, locked-down access), **1 Assisted** (~1 agent — "you + one agent", supervised pair programming), **2 Parallel** (~10 agents — **orchestrator**), **3 Supervised autonomy** (~100 agents — **manager of managers**, an org tree), **4 AI-native** (~1,000+ agents — **VP steering by intent**). The table crosses five columns: number of agents, *what it looks like*, *the bottleneck*, *the products that help*, *the guardrails*. **Central thesis**: consuming more tokens does not move you up a level — advancing to the next stage requires **identifying and breaking the next bottleneck** AND **building the next set of guardrails**. Concretely: giving Claude a trustworthy **self-verification loop** (tests + build + lint + e2e on a real environment), enabling **Auto mode** (avoiding blocking permission prompts), making **code review and security review the default**, adopting multi-agent interfaces (Agent view CLI, Desktop, iOS/Android apps, Tag), then `/loop`, `/batch`, `/goal`, **dynamic workflows** and **worktree isolation** for subagents. On steering: usage (dashboard) measures **activity, not return**; the right question is *"would we have spent engineering effort on this anyway? if so, how many manual engineer-hours would it have cost?"* — that's the ROI. The real payoff arrives when **fixing and maintaining happens in the background** and teams focus on *building*. Anthropic sits at **stage 3, heading toward 4**; Boris Cherny states he has personally reached **level 4**.
#Boris Cherny#Claude Code#Anthropic
Boris Cherny (Creator & Head of Claude Code @Anthropic)
Netflix — Q2 FY2026 shareholder letter: GenAI scales up in production (≈300 titles in 2026), LLMs for discovery and natural-language search, AI tools across the entire advertising cycle (Netflix)
Primary-source tech-watch digest on the position of **Gregor Hohpe** (author of *Enterprise Integration Patterns*, *The Software Architect Elevator*, *Cloud/Platform Strategy*; former AWS & Google Cloud Enterprise Strategist, former Chief Architect at Allianz) regarding the role of the architect in the era of generative AI. Thesis: AI **does not devalue** the architect, it **shifts their value** from code to what AI does not do — **making and owning decisions, arbitrating trade-offs, "selling options," communicating with humans, producing sound abstractions**. Key formula (Craft Conference 2026): "*Developers mainly interact with machines… GenAI. In contrast, architects communicate with humans*". His signature thesis (the architect should not be the smartest person in the room, they should **make everyone else smarter**) grows stronger as code becomes abundant: the advantage comes from **decision discipline** and **surfacing hidden trade-offs**, not from volume. The digest also breaks down his positions by role (enterprise architect: from **cartographer to scout**; software architect: **debugging** decisions rather than writing code; platform architect: **abstractions, not illusions**), his **real options** metaphor (value increasing with technological volatility, Black-Scholes analogy), and his warnings ("*An AI-driven SDLC punishes bad habits much faster*"; the winners of AI will be defined by how fast they move from experimentation to **governed production**). ⚠️ The widely circulated formula "architects who use AI will replace those who don't" **is not from Hohpe**. Domain: software architecture, the architect's role, decision-making, real options, platforms, GenAI in the SDLC.
#Gregor Hohpe#Architect Elevator#role of the architect
Gregor Hohpe (sources primaires) — digest de veille
SFEIR analysis note that reexamines the software architect profession in the age of generative AI through the framework of **Gregor Hohpe** (*The Software Architect Elevator*). Central thesis: the « **Oracle** » architect — the holder of supreme knowledge dictating rules from an ivory tower — is obsolete, since AI generates code and proposals on demand; the modern architect becomes an **intelligence amplifier (IQ Amplifier)** who provides teams with mental models, business context, and decision tools to leverage AI while ensuring system coherence. The document breaks down the impact **floor by floor of the "Architect Elevator"** (Enterprise / Solution / Platform / Software architect) and argues for **Domain-Driven Design (DDD)** as an essential safeguard: the **ubiquitous language** serves as the basis for *system prompts* (a domain dictionary injected via `.clinerules`/templates, reducing hallucinations and business misinterpretations) and **bounded contexts** restrict the scope entrusted to AI to maximize generation reliability. Conclusion: AI is not a threat but a catalyst that relieves the architect of technical grunt work to emphasize synthesis, strategic vision, modeling, and the human link between tech and business. Domain: software architecture, the architect's role, DDD, structured prompting, enterprise AI governance.
#Software architect#architect's role#generative AI
Prasanna Sankar (co-founder/CTO of Rippling, founder of Vorflux) publishes "The Great Flattening" — a manifesto-essay arguing that coding models have become **superhuman** and that the bottleneck has shifted from code production to **encoding judgment** into *agent harnesses*. Everything inside the organization "collapses toward the harness"; everyone's real work becomes *self-profiling*: extracting the tacit decision frameworks from one's head to encode them into the codebase. Simultaneous launch of Vorflux ("autopilot for software engineering"), $15M seed (Y Combinator, Peak XV Partners, Alliance DAO). The essay drew 60,000+ views on X in 24 hours.
#Great Flattening#Vorflux#Prasanna Sankar
Prasanna Sankar (Prasanna S, @myprasanna) — co-fondateur et ex-CTO de Rippling ($16B+ valorisation) · fondateur et CEO de Vorflux AI. Article publié sur X (format long-form article) le 14 juillet 2026 · contenu repris comme manifeste Vorflux (vorflux.com/manifesto).
Message from **Linus Torvalds** on the **linux-media** mailing list (thread "Linking Patchwork with Sashiko?", about an LLM tool for maintainer assistance), in which the creator and **top-level maintainer** of the Linux kernel **officially settles the project's position on AI**. Responding to Roman Gushchin, who pointed out that an adverse message expressed "a very anti-LLM in general" stance, Torvalds agrees ("Yes") and then **flatly denies that this is the kernel's position** ("And no, that's not the position of the Linux kernel"). He **puts his foot down** as the supreme maintainer: **"Linux is not one of those anti-AI projects"**; those who take issue with that can **"do the open source thing: fork it"** — "or just walk away". **Central thesis**: **"AI is a tool, like the other tools we use, and clearly a useful tool"**; that may not have been "so 'clearly' true a year ago, but it's not in question today". He distinguishes questions **still open** ("what the AI economy will actually look like in the end") from the question that is **settled** ("is it useful?") — "anybody who doubts that clearly hasn't actually tried it". He **concedes** that the tool can be **"painful"** — maintainer burden, and the fact that it "keeps finding embarrassing bugs" — but refuses the ostrich posture ("put your head in the sand going 'La La La, I can't hear you'"). **The right response**: make sure **LLM tools _help_ maintainers** rather than causing them pain. **Non-coercion, deliberately**: "nobody is forced to use it, but **I will very loudly ignore those who try to prevent others from using it**". On imperfection: "AI isn't perfect, but hell, anybody who points at its problems had better also point at the mirror" — "**natural intelligence isn't always all that great either**". **Governance framework**: the kernel project "has always been and will remain about **technology**"; the social angle of open source is a "side benefit, not the _point_"; **"this is *NOT* some kind of 'social warrior' project, never has been, never will be"**; "we do open source because it results in **better technology**, not for religious reasons". Program-conclusion: **"we decide based on technical merit first. Not on fear of new tools."** To be read as a **doctrinal position statement** from one of the most influential figures in software — echoing ESR's pro-LLM counter-testimony (another pillar of open source, [[raymond-llm-coding-empowering-2026-07-08]]).
#Linus Torvalds#Linux#Linux kernel
Linus Torvalds ([email protected]) — ingénieur logiciel finlando-américain · **créateur et mainteneur suprême du noyau Linux** (depuis 1991) et de **Git** (2005). Employé de la **Linux Foundation**. Figure centrale et notoirement franche de l'open source · dont la parole sur les mailing lists du kernel fait autorité et jurisprudence dans la communauté. S'exprime ici en sa qualité de **top-level maintainer** pour fixer la position officielle du projet vis-à-vis des outils d'IA. Autres participants au thread cités : Roman Gushchin (linux.dev) · Laurent Pinchart · Mauro Carvalho Chehab · Konstantin Ryabitsev (Linux Foundation) · Steven Rostedt · Stephen Finucane · Jason Gunthorpe · entre autres. (Message de mailing list linux-media ; date : 2026-07-14 ; date d'ajout à la veille : 2026-07-17.)
X post by **Eric S. Raymond** (ESR, author of *The Cathedral and the Bazaar*, co-founder of the Open Source Initiative, ~50 years of coding) — **a frontal counter-testimony to the narrative that "LLMs produce crap code and hallucinate, useless for programming."** His thesis: this **almost never happens to him**, and **not at all anymore over the last two generations** of models he uses ("chat GPT 5.4 and 5.5" under **codex**). The former symptom — a model "going off the rails" as it approaches its context limit — has disappeared: codex now displays a **red warning** prompting the user to **clear the session** instead of spiraling. **Scope of use**: AI applied to **feature changes, refactoring and debugging across 63 projects** in **C, Go, Rust, Python and shell**; documentation writing; **decompiling a DOS binary into readable source**. An established **work routine**: when reopening a project, he first runs the **regression tests**, then starts codex and asks it to **audit the code** (bugs + improvement suggestions). Verdict: LLMs are **"excellent and tremendously empowering"**; their **worst limitation** is **"architectural tunnel vision"** — excellent at generating code to specification, but sometimes **blind to higher-level patterns** — which he takes to be the **job of his "meatbrain."** The strongest, counter-intuitive point: LLMs **do NOT get details and edge cases wrong**; he says he is **worse than them** on this front (despite 50 years of experience), because if a change must **touch five places**, the model **reliably finds all five**, whereas the human fixes four and **spends hours debugging** before finding the forgotten fifth. He then questions the **"downshouters"**: do they live in a **different universe**? Are they using **old, weak models**? Is there a **skill issue** he doesn't see because his **mental habits and communication** fit well with these tools' "handles"? An issue he considers important to settle, since "**billions of dollars would be wasted on misdirected token spend**." His recipe, "very simple": **"Be clear in your thinking, tell the model what you want with precision, and good things happen"** — closing with: "what am I missing here?" To be read as a **pro-LLM counterpoint from a historic figure of open source** to the recurring debate on the (de)valuation of coding agents — echoing the "skill issue" and specification discipline (cf. [[martignole-token-manifesto-2026-07-17]]), and forming a diptych with **Linus Torvalds'** doctrinal pro-AI-tool stance on behalf of the Linux kernel ([[torvalds-llm-outil-kernel-2026-07-14]]).
#Eric S. Raymond#ESR#esrtweet
Eric S. Raymond (ESR, @esrtweet sur X) — développeur · hacker et essayiste américain · **figure historique du mouvement open source**. Né le 4 décembre 1957 à Boston (Massachusetts) ; paralysie cérébrale de naissance · enfance en partie au Venezuela puis en Pennsylvanie. Auteur de l'essai très influent **« The Cathedral and the Bazaar »** (1997, livre 1999) · qui oppose le modèle « cathédrale » (développement centralisé et fermé) au modèle « bazar » (décentralisé et ouvert, à la Linux) ; il a **popularisé le terme « open source »** (contre « free software ») et contribué à convaincre **Netscape** d'ouvrir son code (naissance de Mozilla). **Co-fondateur de l'Open Source Initiative (OSI)** en 1998 · président jusqu'en 2005. A édité le **Jargon File** (*The New Hacker's Dictionary*) · maintenu des projets comme **Fetchmail** · écrit **« The Art of Unix Programming »** (2003). Se revendique **libertarien** · défenseur du port d'armes · ceinture noire de taekwondo ; commente régulièrement tech · politique et open source sur X. Se présente ici comme codeur « très · très bon » avec **~50 ans d'expérience**. (Post X personnel ; date de publication : 2026-07-08 ; date d'ajout à la veille : 2026-07-17.)
An essay by Jean-Paul Paoli (*The Intelligence Fabric*) that shifts the fear of AI at work: the real danger is not **replacement** (the job that disappears) but the **silent unraveling** of team bonds while *everyone stays employed*. Thesis: when every employee makes AI their **first confidant and collaborator**, three "threads" of the organizational fabric come undone without layoffs — **peer-to-peer bonds** (the transfer of tacit knowledge from junior to senior short-circuited), the **manager-employee bond** (early warning signals disappear, the manager becomes "the last to know instead of the first") and **professional judgment** (people stop training those who know how to *do* the work and assess whether the machine is wrong). Paoli names the phenomenon **shadow intimacy** (by analogy to *Shadow IT*) and prescribes not a ban but a deliberate "re-weaving," thread by thread. Domain: management, organizational transformation, AI at work, emotional dependency on models.
In-depth opinion piece (point of view) published on **sfeir.com** on June 24, 2026, by **Didier Girard** (Managing Director, SFEIR). **Central thesis**: in 2024 everyone was betting on **AI4Business** (AI in business processes) as the great value reservoir; by 2026 the picture has **reversed** — it is **AI4IT** (AI to produce the information system: code, SDLC, software factory) that is creating **measurable** value. The article *grounds* this thesis in the firm's tech watch: AI4Business disappointment (the MIT study "95% of pilots without ROI," contested but revealing; an **organizational** blockage / Mollick's Hayekian problem) versus quantified AI4IT evidence (Salesforce, Intercom, Raiffeisen, AWS/Bedrock, Atlassian, DORA). Mechanistic explanation: **code verifies itself** (compilation, tests, CI) whereas business processes have neither a compiler nor an immediate feedback loop. **2027 budget consequence**: a **CapEx→OpEx** shift, token price dynamics (rising peak — Fable 5 at 2× Opus — vs inference ÷280 and downward pressure from open weights/desktop), and **AI FinOps** driven by **cost per outcome**. Closes with **4 recommendations for the COMEX**.
#AI4IT#AI4Business#reversal
**Didier Girard** — Managing Director (CTO / DG) de **SFEIR** · ESN française (~1 000 personnes, France · Belgique · Luxembourg · Suisse). Auteur de l'article ; voix éditoriale du cabinet sur la transformation IA des DSI.
Podcast interview « À la French » (French-language tech channel, recorded at DevSummit) with Mathieu Grymonprez, Global CDO of the Adeo group (Leroy Merlin, Obramat, Weldom). How a century-old family retail group embraces the agentic AI wave: culture vs structure, accountability, token cost and FinOps, enterprise intelligence lock-in, company memory and agent orchestration. Domain: digital transformation, agentic AI, retail, IT strategy.
#Agentic AI#digital transformation#CDO
Mathieu Grymonprez (Global CDO, groupe Adeo) — invité ; Jean-Baptiste Kempf · Steeve Morin · Mehdi Medjaoui (hôtes du podcast « À la French »)
LinkedIn post by Fred Plais (CEO of Archie, ex-Platform.sh): AI made engineers so fast that the **bottleneck moved upstream**, to a place nobody is watching. With execution no longer the slow part, the thinking time that used to exist "while the code was being built" has vanished — the right vision now has to be formed and the right decisions made in a fraction of the time. Two rare profiles are emerging: the one who can **articulate a vision precise enough** for an agent to execute without derailing, and the one who knows how to **orchestrate agents** (anticipating their failures, chaining them, catching an error before it propagates). Hiring for "code output" is becoming obsolete: that is precisely what has stopped being rare. Final thesis: "thinking clearly was always the job — speed just made it impossible to fake".
Case study published by the **Cornell AI Innovation Hub** (June 15, 2026): how a two-semester collaboration between the AI Hub, graduate students, and Cornell's Treasury team turned a time-consuming manual investigation into an AI tool that **recovered $100,000** in unidentified payments on a first batch. A successful **AI4Business** use case (financial process) that illustrates the **Leader-Lab-Crowd** framework of **Ethan Mollick** almost point by point: the **AI Hub** plays the role of the **Lab** (a central, ambidextrous team of technologists plus students); **Treasury** (Cheryl Barnes, Marie Graves…) is the **Crowd** carrying business knowledge and the real pain point; and the **$100,000** constitutes the **visible reward** (vivid win) that anchors adoption — exactly the incentive lever Mollick considers decisive. Key method: **"context first, then plan, then build"** via **Claude Code Plan Mode**, a chain of **fuzzy matching → Gemini Enterprise Web Search → Claude synthesis**, all within the governed **Cornell AI Gateway**. *"The $100,000 is a start."*
#Cornell AI Innovation Hub#unidentified payments#payment reconciliation
**Pete Stergion** — Desktop Engineer au Cornell AI Innovation Hub · co-tech lead du projet (avec Phil Williammee). Article institutionnel signé de l'AI Hub.
Atlassian data study (Inside Atlassian) measuring the actual return of an **AI-native SDLC** powered by **Rovo Dev**. Across 3,400 repositories from 2,500 customers (a quasi-experiment with propensity-score matching), adopting repositories merge **19% more PRs per month**; up to **37-51%** on low/medium-activity repositories and **59-87%** when **3 to 5 members** of the team adopt the tool. On the efficiency side, developers save **2-3 h/week** (≈10% of the 24 hours devoted to coding and review), i.e. 20-30 hours/week reinvested for a team of 10. The thesis: resolve Solow's (1987) "productivity paradox" by shifting from **usage metrics** (tokens) to **impact metrics** (throughput, time saved, failure rate, satisfaction). Recommendation: start with a **team** (not an individual) and measure 2-3 months later.
Pivotal essay by **Dan Shipper** (CEO Every) published on **May 21, 2026** on every.to, *"After Automation"* — an argued response to the thesis of AI-driven collapse of knowledge work. **Pivot thesis**: AI progress creates **more work for humans, not less**. Looping mechanics (***"the commodification cycle"***): (1) AI commoditizes yesterday's human skill; (2) that cheap skill is widely adopted → abundance; (3) abundance produces *sameness* (the *"slop"*); (4) humans demand difference → renewed demand for experts; (5) experts use AI to address today's problems → loop. **Canonical quote**: ***"There's more work to do than ever"***; ***"AI commoditizes the residue of human expertise, creating demand for what's different"***. **Central conceptual framework — Frame vs. Framer**: benchmarks measure performance ***"within frames"*** (specific problem framings); once saturated, *changing the frame resets the counter* — models **escalate within frames but do not replace the framers**. Pivot formula: ***"the frame is not the framer"***. Even at AGI, humans must **specify goals and interpret results** — *"the frame problem regenerates one level up"*. **The "Human Sandwich"**: Human sets frame → AI executes → Human judges and extends. **Two modes of working with agents**: (a) ***agent employees*** — asynchronous delegation (coworker / embedded — Claudie, Andy, Viktor, Fin); (b) ***human-AI collaboration*** synchronous (Claude Code and equivalents). **Every data**: 95% of CEO emails processed by AI; **Fin (Intercom) resolves 65% of support conversations**. **The Zeno's paradox of AI**: AI continuously closes the gap, but humans remain "the turtle ahead" because they are ***"alive to a specific moment"*** — *"running wants, running concerns"* — while models operate on historical training data. **Detailed benchmarks**: **GPT-5.5 = 62/100 on Senior Engineer codebase rewrite** (vs human 80-90s); **GDPval**: 40-49% of expert human level, **but with extensive human framing**. **OpenClaw 44,469 PRs** in May 2026 (vs Kubernetes 5,200 in 2022) — proof that agentic work creates *"more work"*, not *"less human work"*. **AGI implications**: even at AGI, the **human framer** remains structurally ahead — addressing *"current, situated"* problems while the model operates on *"historical training data"*. **Anti-tipping-point pivot conclusion**: this is not a tipping-point event, it is ***a persistent pattern*** that defines the future of work. **Major relevance**: an explicit counter-narrative to *Amodei white-collar bloodbath* / *Sun permanent underclass* / *Anthropic Economic Index* — Shipper, **CEO of a company that lives with agents daily**, offers the theoretical framework that reconciles the two empirical observations (AI does more + humans remain indispensable). Strong convergence with **Ng "No AI jobpocalypse"** (2026-05-08), **Mollick × roon ASI / FDE** (2026-05-10), **Tatsyi/Raiffeisen "AI made engineers different"** (2026-05-05), **Curran/Intercom 3× R&D** (2026-04-16) — all describing humans as *redeployed toward framing* rather than *replaced*. Productive tension with **Sun NYT permanent underclass** (2026-04-30), **Wallace-Wells AI populism** (2026-05-08), **Osmani Cognitive Surrender** (2026-05-05 — the human framer must remain active). To be leveraged for COMEX / DG / boards: strategic vocabulary for 2026 — *"frame vs framer"* becomes the canonical grid for AI governance.
#Dan Shipper#Every#after automation
**Dan Shipper** — CEO et co-fondateur de **Every** (média / studio AI-native, créateur de la newsletter *Every*, propriétaire du framework et plugin *Compound Engineering* — cf. fiche `shipper-klaassen-compound-engineering-every-agents-2025-12-11.md`). Profil rare : **opérateur-théoricien** · dirige une organisation entièrement augmentée par l'IA (95 % emails CEO automatisés, agents Claudie/Andy/Viktor en production, Fin pour le support) tout en publiant régulièrement des essais conceptuels sur every.to. Voix éditoriale anglo-saxonne de référence dans le corpus 2025-2026 sur les **modes de travail humain-IA**. Article publié sur **every.to/p/after-automation** le **21 mai 2026**.
Pivot article **Ivan Chepurin & Travis Turner** (Evil Martians Chronicles, **May 19, 2026**) — ***« AI-assisted engineers are burning out, is this fine? »*** — **structured diagnosis of burnout among AI-assisted developers** and a **5-axis intervention toolkit**. **Pivot thesis**: AI-accelerated productivity hides a **hidden cost — developer exhaustion**. *« Higher productivity doesn't translate to sustainable work practices or job satisfaction. »* Shunryu Suzuki epigraph on mental agitation. **TL;DR — 3 essential remedies**: (1) restore enjoyment of the process, (2) rebuild accomplishment / ownership / pride, (3) remove the pressure of continuous productivity maximization. **Central narrative frame — Ben vs Alice**: Ben (traditional coding) = 4 h of steady work, distributed cognitive load, satisfaction at completion; Alice (AI-assisted) = 2 h of cognitively high-intensity work, continuous task-switching, **no satisfaction** + fills the freed-up time with more tasks → **exponential escalation of load** despite accelerated output. **Canonical formula**: ***« We compensate for a lack of satisfaction with work quantity. »*** **Structural disruption of the craft cycle**: (planning → crafting → result) compressed into (planning → result), removal of the meditative craft phase replaced by **cognitively demanding code review**. Direct convergence with **HBR study 2026** (cited): *« cognitive exhaustion from intensive oversight of AI agents is both real and significant »* + **UC Berkeley research 2026**: workers fill natural breaks with AI tasks. **Quiet career change** — pivot concept: developers hired to code now do **different work without a conscious career transition**. 4 possible paths: (1) find enjoyment in the new structure (prioritized), (2) ignore AI, (3) work without enjoyment (unsustainable), (4) change careers. **5 daily burnout factors identified**: (1) ***Losing context*** — the agent carries project understanding externally, cognitive-debt shift from code to people, loss of system intuition; (2) ***No time for passive thinking*** — *« The model fills the silence before your own thinking has a chance to connect dots »* (showers, walks eliminated as moments of unconscious problem-solving); (3) ***False expectations*** — initial speed = unrealistic baseline, subsequent slowdowns experienced as failure; (4) ***Review bottlenecks*** — *« the more code is generated, the more code needs to be reviewed »*, disproportionate cognitive load on seniors, diffusion of responsibility; (5) ***Endless possibilities*** — low prompting friction encourages constant pivots, absence of natural scoping. **5-intervention toolkit**: (a) **Acknowledge your wins** (win-log, team demos, hours tracker); (b) **Rethink AI workflow** (planning > review, **3-4 iterations max**, no parallel task-switching, separate AI-heavy tasks with breaks, decompose); (c) **Keep exercising your craft** (protected AI-free craft hours, *« ask » mode > generation mode*, agents off on passion projects); (d) **Discipline + work-life balance** (fixed hours, real breaks, daily intentions, stop when done); (e) **Find new areas of interest** (user research, soft skills, analytics, agent fine-tuning + guardrails, perf optimization). **Conclusion**: *« AI can be helpful. Problems appear only if you misuse it. »* Industry evolution = inevitable; individual well-being = controllable. Major convergence with **Osmani Cognitive Surrender** (2026-05-05), **Frizzo "Year With Claude Code"** (2026-05-05 — *« writing muscle atrophy »*, *« deep flow rare »*), **Bedard BCG/HBR Brain Fry** (2026-03-05 — 1,488 employees, peak of 3 tools, +39% errors, +39% intent to leave). Major relevance for **CTO / VP Engineering / IT HR** dealing with the retention of AI-augmented engineers in 2026.
#Ivan Chepurin#Travis Turner#Evil Martians
**Ivan Chepurin** & **Travis Turner** — auteurs Evil Martians (cabinet de conseil ingénierie indépendant, Berkeley/global, ~150 ingénieurs, spécialiste Ruby on Rails / React / produits SaaS depuis 2010 ; éditeurs du blog *Evil Martians Chronicles* — référence dans la communauté Rails et JS). Article publié dans la catégorie **AI / Developer Community** sur evilmartians.com le **19 mai 2026**. Profil Evil Martians : voix éditoriale **opérateur-praticien** · articles longs ancrés dans le terrain produit · registre **soin du craft + lucidité business** · public habituellement développeurs / CTO / fondateurs early-stage.
Launch of **AI/works™**, an **agentic development platform** claimed by **Thoughtworks** to be *"the new standard for building and running industrial-grade systems in the AI era."* The core pitch is **economic**: *"the old model made you pay millions to build, run, then pay again to rebuild — AI/works™ ends that routine."* The platform covers **the entire SDLC** around a central concept, the ***Super Spec*** (a dynamic, unified specification covering architecture, workflows, security, data, UX), with **six capabilities**: Reverse Engineering (legacy → as-is specs), Dynamic Spec Development (raw requirements → Super Spec), Spec to Code (coordinated agents generating testable code), Developer Experience (governed golden paths), Control Plane (agent orchestration with cost transparency, active guardrails, end-to-end lineage), Runtime Ops (continuous monitoring detecting change, updating the Super Spec, regenerating impacted code). **3-3-3** methodology: 3 days to align on the product concept, 3 weeks for the prototype (desirability/viability/feasibility), 3 months for MVP in production. **Constellation Research** recognition: *"changing the economics of enterprise software delivery"* via a *"spec-driven, lifecycle"* approach. Opening tagline: ***"We are doing it again for the AI era"*** — invoking Thoughtworks' XP/CI-CD/microservices heritage. Anti-hype positioning: *"stands on an engineering foundation rather than enthusiasm"*, *"no consultant crowds"*, *"finance can open the bill without switching on emergency lighting."* Featured partners: AWS, GCP, Azure, Databricks, Snowflake + Claude, OpenAI, DeepSeek, Gemini, Grok + NVIDIA, Groq, Stripe, Spotify, CAST, Cyn DX, Mechanical Orchard.
#Thoughtworks#AI/works#AI works trademark
**Thoughtworks** (auteur collectif corporate, page produit/marketing). Aucun individu cité sur la page. Contexte des figures Thoughtworks pertinentes en arrière-plan : **Martin Fowler** (chief scientist emeritus, *Refactoring*, *Patterns of Enterprise Application Architecture*) · **Rebecca Parsons** (CTO emeritus) · **Birgitta Böckeler** (Distinguished Engineer, *Harness Engineering for Coding Agents*, fiche 2026-04-02) · **Matt Kamelman** (*Service-as-Software*, fiche 2025-12-03) · **Sam Newman** (*Building Microservices*).
Ethan Mollick's (Wharton) consistency test: we'll know AI labs truly believe in ASI the day they dissolve their *Forward Deployed Engineering* (FDE) teams. Public debate with roon (OpenAI) on LinkedIn: roon objects that this is a **hayekian problem** (intelligence does not automatically resolve organizational information flow) and revives the term "**Gentle singularity**". Consensus in the comments: technology is the easy part; internal politics / legacy workflows / contractual liability are the real bottleneck. Marker phrase: *"Curing cancer might be easier than replacing Accenture"*. Epistemic **East Coast vs West Coast** opposition on the trajectory of AI adoption.
#ASI (Artificial Super Intelligence)#Forward Deployed Engineering (FDE)#AI consulting
Televised debate on BFM Business (*Tech & Co Business* program, "The Debate" segment, 17 minutes) with **Rémi Jacquet** (CEO of Cast Software France, founder in 2023 of a think tank of about a hundred CIOs on the impact of generative AI on development, partnership with Cigref / Epita) and **Didier Girard** (CTO and CEO of **SFEIR**, a French IT services company (ESN) of about 1,000 people). Strong theses: *"writing code has become an anti-pattern"* (Girard), AI produces code of higher quality than most engineers and is *"2 to 10× more efficient"* — this is a reality, but the profession is not disappearing. The developer becomes a **conductor / agent manager / arbiter**, 14-day sprints are replaced by one-hour to half-day ***bolts***, the **Pizza Team** (8-10 people) no longer works in the agentic era, a new role is emerging — the ***product engineer*** —, the lifespan of a skill drops from **10 years to 1 year**, and **token** consumption becomes the *fuel* of value creation (NVIDIA anecdote allegedly paying bonuses in tokens, taxi driver metaphor for a driver who doesn't consume gas). SFEIR claims *"1,000 people, production capacity of 10,000"*. On the Cast side: positioning on ***harness engineering*** (deterministic vs probabilistic AI, control and guardrails), aligned with Sylvain Duranton's (BCG X) op-ed in *Les Échos* stating that *"an agent = an LLM + harnesses"*. Historical pivot: 2024 *prompt engineering* → 2025 *context engineering* → 2026 *harness engineering*. Key warning: *"the stronger AI becomes, the more we let our guard down — the more risks there are"* (Jacquet). Pivotal role of HR in the transformation, complete overhaul of the SDLC, recommendation to juniors to solidify software architecture fundamentals (*"code is the score, you need to master the symphony"*).
LinkedIn Pulse op-ed by Alexandre Frizzo after a year of daily use of Claude Code, offering a **nuanced assessment** rare in the 2026 corpus — productivity **multiplied by 3-5×** in his case (consistent with Wescale, and in line with the median of committed practitioners; the elite tail goes much higher, cf. Cherny *few dozen PRs/day + 150 PRs record* and Karpathy *"peaks much higher than 10×"*), but **hidden cognitive costs** acknowledged. Pivot thesis: ***"the new bottleneck is supervision"*** — the job has changed shape, one no longer *writes* code, one *decides* about code generated by agents. Gains: 3-5× output, previously infeasible projects now achievable (yak-shaving, boilerplate), near-zero cost of experimentation. Acknowledged losses: ***"writing muscle"*** atrophied (manual code now feels *effortful*), **rare deep flow state** (constant context-switching between supervisions), **diminished ownership satisfaction** (*"code is good, but isn't quite mine"*). Unresolved tensions: **FOMO** (*"every hour I'm not at the keyboard is an hour an agent could be earning for me"*), **review quality** at 3-5× volume, **skill atrophy**. Statistics cited: median 3-4h effective coding out of an 8h day, **23 min** context recovery per interruption (Gloria Mark study), 15-25 min flow entry, 500% productivity in flow (McKinsey). Exemplary epistemic position: simultaneously rejects the *"AI is bad"* narrative and uncritical enthusiasm. A welcome counterweight to Cherny's *"coding is solved"* (2026-05).
#Alexandre Frizzo#LinkedIn Pulse#year with Claude Code
Alexandre Frizzo (auteur LinkedIn Pulse, identité tech non précisée par le post au-delà du nom — auteur d'une tribune one-year retrospective Claude Code).
Methodology article by Antoine HABERT (WEnvision) that formalizes **PROJ-AI**: a lightweight methodological layer so that collective projects become transferable rather than dying with their deliverable. Structuring triad: a **version-controlled git repo** (single source), an **AI agent** (Claude Code, Cursor) that reads the doctrine at every session, and a **markdown doctrine** specifying decision protocols and agent behaviors. Six directory zones (DOCS/, IDEAS/, DR/, OUT/, DOCTRINE/, AGENT/), operational **DPEV** cycle (Decide → Promise → Execute → Verify), Decision Records scored across 7 dimensions, dual interface (business Studio + tech CLI/IDE), five agent directives, and a shared **proj-ai-commons** library that bootstraps a project in 30 minutes vs. 1 week. Metrics across 3 engagements: onboarding **3 weeks → 2 days**, structural decisions tracked **30% → 100%**, architecture doc compilation **6 weeks → continuous**. Central aphorism: ***"The project is not a byproduct of the deliverable. The project IS the deliverable."*** Explicit stance: technology 20%, **team discipline 80%**.
#Antoine HABERT#WEnvision#PROJ-AI
Antoine HABERT (WEnvision — cabinet français de conseil en stratégie et IA agentique).
Medium op-ed by **Hryhorii Tatsyi** (CTO, **Raiffeisen Bank Ukraine**, ~900 IT engineers) reporting a **12-month longitudinal study** (May 2025 → April 2026) on the real impact of generative AI in a large European bank. Pivot thesis: ***"AI didn't make our engineers just faster. It made them different."*** Unlike individual accounts (Frizzo, Cherny) or meta-level ones (Curran/Intercom), this is a **quantified organizational assessment from a traditional regulated bank** — a corpus still rare in 2026. Results: **−75 people (−8% headcount, including 64 engineers)** over 12 months, yet **more code shipped, fewer incidents, improved security**; AI adoption **62% → 83%**; **68% of engineers receive ≥50% of their code via AI assistance**; **new-engineer onboarding 60-90 days → ~40 days** (consistent with Anthropic data of 82→40 days). Three emerging archetypes: (1) **Copilot-only** +10-25% on PRs, same scope; (2) **Multi-tool** story points ×1.5-3, cross-repo scope +50-80%; (3) **Claude on corporate stack** code volume ×4.5, radically expanded scope. **Seven AI products built** that did not exist before: Service Knowledge Hub (57 microservices, 83 releases/month), Mobile Android workflow CI plan/implement/test, AI Agent Portal (2,085 users / 649 MAU in 87 days, MCP generation via OpenAPI specs), Shift-left Security Plugin (−82% exposed secrets), DevPortal Backstage + Kubernetes diagnostics agents (−68% critical incident resolution time), DRAIF MCP text-to-SQL Data Lake with 10,000 tables (embedding fine-tuned 2× OpenAI), Call Evaluation (>97% transcription accuracy, voted best product in the Raiffeisen group). Stability: **blocking incidents −70%, critical resolution −68%, high-severity security alerts resolved +155%**. Central strategic insight: ***"AI expanded our production possibility frontier, and we deliberately allocated the freed capacity"*** — AI does not do the same thing faster, it shifts **what one can decide to do**. The evaluation question to reframe: not *"by how much % did existing KPIs increase"* but ***"what your engineers built that didn't exist before"***. AI lifts underperformers to baseline more than it accelerates top performers; **senior architects return to active development** after years away from it. Major relevance for banking/insurance/regulated-sector executive committees (Raiffeisen = bank, Ukraine = wartime context + operational resilience).
#Hryhorii Tatsyi#Raiffeisen Bank Ukraine#CTO bank
**Hryhorii Tatsyi** — CTO de **Raiffeisen Bank Ukraine** (filiale ukrainienne du groupe bancaire autrichien Raiffeisen Bank International, RBI). Auteur Medium @milhibisidek. Profil discret côté visibilité publique (25 followers Medium au moment de la publication) · mais position institutionnelle de premier plan : il dirige une organisation IT d'environ 900 ingénieurs dans une banque systémique opérant en contexte ukrainien (économie de guerre depuis 2022, résilience opérationnelle critique). L'article est sa première contribution publique d'envergure documentée sur cette plateforme.
Wescale (France) presentation formalizing the ***Augmented Software Factory*** doctrine: a software value chain entirely orchestrated by specialized AI agents across six production lines (Intent/PRD-ADR → Plan/User Stories → **human sign-off** → 24/7 Production → Independent audit verification → DevOps Deployment), where humans intervene at only two precise moments. Strong theses: the return of the **predictable V-cycle** against Scrum, realistic **3-4x** gains (not 10x), the shift from *code producer* to ***Strategic Judge*** and from *solo developer* to ***Agent Manager***, DORA metrics replacing velocity, maximum ROI on legacy modernization and costly SaaS replacement, and above all ***injected governance*** as a "near-military layer" that constitutes the central innovation and the real barrier to entry. Built by eating its own dogfood: *"What we learned building Solario on Solario."*
#Wescale#Augmented Software Factory#augmented production chain
Wescale (cabinet français de conseil tech / cloud / DevOps) — auteurs collectifs (présentation corporate, pas d'auteur individuel cité dans le deck).
Les Echos (Florian Dèbes) report from San Francisco: AI agents already integrated as colleagues in start-ups, "petri dish" (Aaron Levie / Box), Claude reflex before every meeting, personal Jarvis, 5 parallel agent tabs, "the limiting factor is human cognition" (Patrick Joubert / Rippletide), "brain fry" / cognitive overheating, BCG/HBR study putting 14% of employees overwhelmed, "token-max" ranking mode for the biggest AI users, testimonials from Sinaï/Bangay/Allali/Hodjat/Pantera/Chapeau and an echo of Siddhant Khare ("AI reduces production costs but increases coordination costs").
#Silicon Valley#San Francisco#AI agents as colleagues
Florian Dèbes (Les Echos, rubrique Travailler mieux / Vie au travail)
Revamp of the engineering hiring process at Sierra in the age of coding agents: AI-native onsite interview (Plan/Build/Review), removal of the algorithmic coding test, replacement of the phone screen with a system design interview, pilot of a debugging interview on an existing codebase.
Joint **DORA × delta** report (Google Cloud Professional Services), 60 pages, version **v. 2026.1** (citations February 2026, PDF created April 21, 2026), license **CC BY-NC-SA 4.0** — the first official **DORA ROI** framework dedicated to AI in the SDLC, with an **interactive calculator** at dora.dev/ai/roi/calculator. Pivotal thesis: ***"AI is an amplifier"*** — AI **amplifies** simultaneously the strengths of high-performing organizations and the dysfunctions of struggling organizations; it does not create performance, it **multiplies it where it already exists**. New central concept: the ***J-Curve of AI value realization*** — every AI adoption goes through a **temporary productivity dip** (learning curve + verification tax + pipeline adaptation) before **exponential growth**, a metaphor for the *"tuition cost of transformation"* to be **explicitly budgeted**. Reference calculation: organization of 500 FTE / fully loaded salary $176k / 12.5% time saved per developer (≈ 1h/8h day) → **value $11.6M / investment $8.4M / ROI 39% / payback period 8 months (0.7 year)**. Modeled costs: licenses ($250/user/year), additional API ($80/user/year), training ($9,600/user/year), infra ($100k/year), J-Curve cost ($3.3M for a 15% drop over 3 months). Modeled value: **headcount reinvestment capacity** ($11M — freed capacity to reinvest, **NOT headcount reduction**), revenue from extra feature deployments ($990k, based on a 33% idea success rate, Larsen 2023), **negative downtime impact** (−$344k, "instability tax"). **Explicit reinvestment strategy**: ***"we strongly recommend organizations do not adopt a headcount-reduction strategy"*** — reinvest in innovation, retain talent, capitalize on institutional knowledge. Five pillars of value: Productivity / User Experience / Cost Efficiency / Developer Experience / Business Growth (from most direct to most indirect, *cumulated business value*). Five systemic keys of adoption: **Trust + Platform + Data + Users + Guardrails**. Two-phase roadmap: (1) **Build context layer (CapEx)** — quality IDP + healthy data ecosystems; (2) **Empower human in loop (OpEx)** — context engineering + trust in AI. Indicators: leading = experiment frequency + deployment frequency; stability gauge = change failure rate + rework. Three scenarios to model (Conservative 0.8 value × 1.5 cost / Realistic 1.0 / Optimistic 1.2 × 0.8). External data mobilized: 78% of executives report ROI on ≥1 gen AI use case (Google Cloud), 88% of early agentic AI adopters see positive ROI, **35-40% greenfield productivity vs ≤10% brownfield/legacy** (Stanford), inference cost ÷280 between Nov 2022 and Oct 2024 (Stanford AI Index 2025), **727% ROI over 3 years** for Google Cloud AI customers, average market AI payback of **8 months**. Acknowledged weaknesses: *"all models are wrong"* — the model needs contextualizing, the calculator needs adjusting; risk of double-counting value (time saved → both avoided hire AND extra revenue); a "loose" user experience link, hence excluded from the calculator. **Deontological insight**: ***"We don't measure AI by the code it writes but by the bottlenecks it clears"*** — measured by bottlenecks cleared, not code volume. **Major relevance** for CIOs/CTOs who need to build a defensible AI business case for a CFO/board; for France/Europe, to be articulated with Wescale (realistic X3-X4), Tatsyi/Raiffeisen Bank Ukraine (bank case study, −75 people but deliberate reinvestment), Frizzo (3-5× median), Curran/Intercom (3× R&D over 16 months), DORA Report 2025 (on which this ROI builds).
#DORA ROI of AI-assisted software development#Google Cloud DORA report 2026.1#J-Curve of AI value realization
Rapport conjoint **DORA team × delta team** (Google Cloud Professional Services). Auteurs principaux : **Eva Dong** (AI Value Realization Americas, ex-McKinsey 8 ans, Master Financial Engineering Michigan) · **Andre Ellis Jr.** (Cloud Financial Operations Lead, Morehouse + Wharton MBA) · **Nathen Harvey** (DORA team lead, co-auteur multiples DORA reports + 97 Things Every Cloud Engineer Should Know) · **Vivian Hu** (10X Technology Consultant, contributrice DORA 2025 State of AI-assisted Software Development) · **Ursula Lübbert-Passing PhD** (AI Value Realization EMEA, 20 ans benchmarking + value advisory, PhD effort estimation software projects) · **Eric Maxwell** (lead 10X Technology consulting, ex-Chef Software, contributeur DORA) · **Aaron Wanjala** (cloud developer advocate Spring Boot/Angular). Conseillers et contributeurs : **Ben Jose · Eric Lam · Matt Orr · Allison Park · Ryan J. Salva · Jerome Simms · Dave Stanke · Cedric Yao**. Design : Human After All (humanafterall.studio). Document publié sous licence **CC BY-NC-SA 4.0** · version v. 2026.1 · citations retrieved February 2026.
Episode #351 of the French-language podcast **If This Then Dev** (Bruno) with **Julien Lépine**, Chief Technology Officer of **AWS France** (13 years at Amazon), recorded on the sidelines of the **AWS Summit Paris** (April 1, 2026, ~10,000 attendees). Pivot thesis: in the agentic era, writing code becomes secondary, and value shifts toward **understanding context, architectural trade-offs, and human accountability**. Central proof point: the **redevelopment of Amazon Bedrock** — a critical platform handling thousands of billions of requests — by a team of **6 people in 72 days** (vs. an estimated 30 people / 18 months), **code entirely generated by AI**, without vibe coding. AWS is **standardizing internally on Kiro** (IDE + CLI, running on Claude Sonnet/Opus) for ~30,000 developers (announced by Matt Garman at re:Invent). Throughline: **keeping control** without reviewing everything — via **formal modeling (TLA+)** and **Raisonnement automatisé** to prove invariants and bound agents, **blameless post-mortem**, and the principle that "responsibility for an agent's action rests with the person operating it." Emergence of the **AI DLC** (sprints → multiple daily **Bolts**) and the risk of **cognitive overload / burn-out**.
#AWS Summit Paris#Amazon Web Services#code agents
**Julien Lépine** — Directeur de la technologie (CTO) d'Amazon Web Services France · 13+ ans chez Amazon ; ses équipes accompagnent les clients AWS sur le cloud · la data et l'IA. **Hôte** : Bruno (créateur et animateur du podcast *If This Then Dev*).
BCG-HBR study (Bedard, Kropp, Hsu, Karaman, Hawes, Kellerman) of 1,488 US employees, January 2026: formal definition of ***AI brain fry*** (acute cognitive fatigue linked to AI oversight), 14% of AI-using workers affected (Marketing 26%, Legal 6%), productivity peaks at 3 simultaneous tools, +33% decision fatigue / +39% major errors / +39% intent to leave among the "brain fried," empirical distinction between **burnout** (emotional, eased by AI on routine tasks -15%) and **brain fry** (acute cognitive, worsened by oversight). 5 recommendations for leaders, "AI orphan tax" (+5% fatigue when the manager expects the employee to figure it out alone), org work-life balance -28%. Pivotal academic source cited by Les Echos and the 2026 debate.
Thoughtworks retreat on the future of software development with LLMs — reflections on organizational impact, cognitive debt, and supervised programming
AI benchmarking beyond standard tests - Interviewing AI models for specific use cases - Jagged Frontier - OpenAI GDPval - Vibes vs real measurements - GuacaDrone example - Ethan Mollick - One Useful Thing
Deep Research - AI4* Revolution - 6 pillars of software production - Copilots→Agents transition - Vibe vs Check paradox - FinOps for AI crisis - Governance as critical path - GenAI Landing Zone
Practical AI usage guide, model selection, jagged frontier, Centaurs vs Cyborgs, OpenAI usage data, Claude/Gemini/ChatGPT - Ethan Mollick
#AI model selection#ChatGPT vs Claude vs Gemini#jagged frontier
Ethan Mollick (Associate Professor, Wharton School, University of Pennsylvania ; Auteur "Co-Intelligence: Living and Working with AI" ; TIME 100 Most Influential People in AI 2024)
Josh Bersin panorama on the pivotal role of CHROs in AI transformation: interview with Patricia Frost (Seagate) "Leave No One Behind", peer quotes (Jacqui Canney/ServiceNow, Tracey Franklin/Moderna, Helen Russell/HubSpot, Kathleen Hogan/Microsoft), 4 strategies (AI readiness, platforms, hiring/redeployment, supermanagers), thesis "AI transformation is not about technology: it's about work, jobs, and people."
#CHRO#Josh Bersin#AI transformation
Josh Bersin (analyste RH et consultant, fondateur de The Josh Bersin Company) · citations de Patricia Frost (CHRO Seagate)
Legal.io relay of the MIT NANDA study "The GenAI Divide: State of AI in Business 2025": 95% of enterprise AI pilots deliver no measurable ROI despite $30-40B invested. Concept of the "GenAI Divide", "shadow AI economy", four structural failure factors, back-office and build-vs-buy recommendation. Empirical justification for the HR-organizational shift.
#MIT NANDA#GenAI Divide#95% pilot failure
Legal.io (relais et synthèse) — étude MIT NANDA "The GenAI Divide: State of AI in Business 2025"
Valence summary of the virtual summit "AI & the Workforce: The Adoption Gap": Ethan Mollick lays out the Leader-Lab-Crowd framework, coins "HR is R&D now," and argues that the AI "shadow economy" and the collapse of the apprenticeship model force CHROs to become the architects of the transformation. Five actionable experiments for writing the AI-HR playbook.
#HR is R&D now#Leader Lab Crowd framework#Ethan Mollick
Alex McMurray (Valence) — synthèse de l'intervention de Ethan Mollick au sommet Valence "AI & the Workforce: The Adoption Gap"
Exclusive interview with Tracey Franklin (Chief People and Digital Technology Officer at Moderna) on the merger of HR and IT into a single department: the shift from siloed "workforce planning" and "technology planning" to integrated "work planning," the "architect the flow of work" metaphor, 3,000+ custom GPTs, 5,000 employees, and a 2030 vision of an adaptive human+agent organization.
#HR-IT merger#Moderna#Tracey Franklin
Allie Nawrat (UNLEASH) · interview de Tracey Franklin
OpenAI's official case study on the ChatGPT Enterprise deployment at Moderna: 750 GPTs in 2 months, 100% legal adoption, the Dose ID GPT for clinical trials, Stéphane Bancel's "100,000 employees" quote, an organizational transformation framework (mChat, Generative AI Champions, an internal forum with 2,000 participants).
#Moderna#OpenAI#ChatGPT Enterprise
OpenAI (étude de cas officielle, citations Stéphane Bancel, Brad Miller, Brice Challamel, Shannon Klinger, Kate Cronin, Meklit Workneh)
Op-ed by **Olivier Rafal** (Consulting Director Strategy at **WeNvision**) published on **February 23, 2024** on **CIO-Online** (*Tribune* section), advancing a thesis still counter-intuitive at the time: **generative AI is more a matter of technology product than an AI/data science project**. **Argument 1 — data science is not the core issue**: building a *foundation model* from scratch requires *« several months, millions of euros, and access to enormous quantities of data »* — reserved for players with specific, monetizable datasets (e.g. **Bloomberg** and its **BloombergGPT** for finance). For nearly all companies, the right reflex is therefore not to hire data scientists. **Argument 2 — skills mismatch**: what is mainly needed is **development and integration engineers** (back/front), **strong cloud skills**, and **DevOps**. Client quote: *« You don't necessarily need to be a data scientist, but you need to understand the basic concepts, have back-office development skills, and strong cloud skills. »* **Argument 3 — platform architecture (orchestrators + APIs)**: building an enterprise **plateforme d'IA générative** via orchestrators and APIs makes it *« possible to work with the best LLMs on the market and switch between them as their respective capabilities evolve, without reworking the applications »* (anti vendor lock-in). **Argument 4 — from project to product**: *« The platform […] must be regarded as a product in its own right »*; instead of a one-off investment, plan for a **monthly funding stream** (continuous iteration, ongoing innovation). **Argument 5 — governance & shadow AI**: the unprecedented democratization of GenAI generates *« as much shadow AI as strong expectations toward the CIO office »* → governance to capture business needs, **prioritize products by value**, and oversee proper operation. **Paradigm shift** announced: *« the shift is from classic algorithmic programming to agents Langchain that handle part of the decisions »*. **Relevance to the watch**: a **founding text (2 years ahead)** of WeNvision's doctrine (product > project, platform/API, flow-based funding, governance, shadow AI), later extended by [[wenvision-ai-agents-enterprise-deployment-2025-10-01]], [[habert-ia-agentique-production-2025-10-29]], and rafal-wenvision-tokenomics-foundation-finops-ia-2026-06-04 (FinOps/token, flow-based funding → financial governance). It also foreshadows the *harness/platform around the model* (Dropbox/Okumura: *systems around the model*) and **model independence** achieved through an orchestration layer.
#generative AI#technology product#product vs project
**Olivier Rafal** · *Consulting Director Strategy* chez **WeNvision** (cabinet de conseil FR). Tribune publiée dans la rubrique *Tribune* de **CIO-Online**. Auteur déjà présent dans la veille (cf. fiches WeNvision/Atlas/Tokenomics). Publié le **23 février 2024**.
Crisis of Meaning at Work - "Help me write" Button - Setting Time on Fire - Effort Signals - AI Recommendation Letters - Ethan Mollick - One Useful Thing