How teams and organizations adopt AI-assisted development.
62 fiches · 113 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
In-depth opinion piece published on **sfeir.com** on June 24, 2026, authored by **Didier Girard** (Managing Director, SFEIR). **Central thesis**: in 2024 everyone was betting on **AI4Business** (AI in business processes) as the great reservoir of value; by 2026, the assessment has **flipped** — it is **AI4IT** (AI for producing the information system: code, SDLC, software factory) that creates **measurable** value. The article *grounds* this thesis in the firm's watch: AI4Business disappointment (MIT study "95% of pilots without ROI," contested but revealing; **organizational** blockage / Mollick's Hayekian problem) vs. 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 pricing dynamics (the ceiling rising — 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 COMEX recommendations**.
#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 approach 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 changes, updating the Super Spec, regenerating impacted code). **3-3-3** methodology: 3 days to align the product concept, 3 weeks for the prototype (desirability/viability/feasibility), 3 months for a production MVP. **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 op-ed by Alexandre Frizzo after one 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 with **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*), **deep flow state rare** (constant context-switching between supervision tasks), **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 over an 8h day, **23 min** context recovery per interruption (Gloria Mark study), 15-25 min to enter flow, 500% productivity in flow (McKinsey). Exemplary epistemic stance: simultaneously rejects the *"AI is bad"* narrative and uncritical enthusiasm. A salutary 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.
Presentation by Wescale (France) that formalizes the doctrine of the ***Augmented Software Factory***: a software value chain entirely orchestrated by specialized AI agents across six production lines (Intention/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 substitution, and above all ***injected governance*** as a "near-military layer" that constitutes the central innovation and the true barrier to entry. Built by eating its own dogfood: *"What we learned by 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 report (Florian Dèbes) from San Francisco: AI agents already integrated as colleagues at start-ups, "petri dish" (Aaron Levie / Box), reflex use of Claude 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 showing 14% of employees overwhelmed, "token-max" ranking of the heaviest AI users, testimonials from Sinaï/Bangay/Allali/Hodjat/Pantera/Chapeau and an echo from Siddhant Khare ("AI reduces production costs but raises 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 retrieved February 2026, PDF created April 21, 2026), licensed **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. Pivot thesis: ***"AI is an amplifier"*** — AI **amplifies** the strengths of high-performing organizations and the dysfunctions of struggling ones simultaneously; 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 **budgeted explicitly**. Reference calculation: a 500 FTE organization / $176k fully loaded salary / 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 costs ($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 to 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 leveraged: 78% of executives report ROI on ≥ 1 gen AI use case (Google Cloud), 88% of early agentic AI adopters see positive ROI, **35-40% productivity greenfield 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 **8-month** payback in the AI market. Assumed 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); the user experience link is "loose" and therefore 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 by code volume. **Major relevance** for CIOs/CTOs needing to build a defensible AI business case in front of a CFO/board; for France/Europe, to be read alongside 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 (which this ROI report builds on).
#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), which puts forward a thesis that was still counterintuitive at the time: **generative AI is more a matter of technological product than of an AI/data science project**. **Argument 1 — data science is not the core of the 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 — a skills mismatch**: what's mainly needed are **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 do need to understand the basic concepts, have back-office development skills, and strong cloud skills. »* **Argument 3 — platform architecture (orchestrators + API)**: building an enterprise **plateforme d'IA générative** via orchestrators and API makes it *« easy to work with the best LLMs on the market and switch between them as they each evolve, without reworking the applications »* (anti vendor lock-in). **Argument 4 — from project to product**: *« The platform […] must itself be considered a product »*; instead of a one-off investment, plan for a **monthly funding stream** (continuous iterations, ongoing innovation). **Argument 5 — governance & shadow AI**: the unprecedented democratization of GenAI generates *« as much shadow AI as strong expectations toward the DSI »* → governance to capture business needs, **prioritize products by value**, and oversee proper operation. **Paradigm shift** announced: *« we are moving from classic algorithmic programming to agents Langchain that handle part of the decisions »*. **Relevance for the watch**: a **founding text (2 years ahead)** of WeNvision doctrine (product > project, platform/API, flow-based funding, governance, shadow AI) that the fiches [[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]] will extend (FinOps/token, flow-based funding → financial governance). It also prefigures the *harness/platform around the model* (Dropbox/Okumura: *systems around the model*) and **model independence** through an orchestration layer.
#generative AI#technological 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