Video interview recorded at **VivaTech** (**Scaleway** booth), broadcast by the media outlet **République**, bringing together **Damien Lucas** (CEO of Scaleway) and **Franck Le Moal** (Global Technical Officer of the **LVMH** group). **Central thesis**: the emergence of a **"tech geopolitics"** is forcing multinationals to abandon the single global solution in favor of an **information system regionalized into three blocs** (United States, Europe, China). LVMH (€80bn in revenue, 75 maisons, 100+ countries) formalizes a **cloud partnership with Scaleway** to build an **autonomous European building block**, alongside Google Cloud (data, since 2021), SAP, Salesforce on the Western side and Alibaba Cloud / Huawei / Tencent on the Chinese side. The group describes itself as **"hybrid"** and **autonomous** rather than **"sovereign"** (a word it rejects, deemed ambiguous). Scaleway positions itself as a **European cloud provider** immune to extraterritorial laws and protected against a **kill switch** ("not science fiction," given the weekend's news). Damien Lucas's economic argument: **€1 spent with Scaleway = 68 cents that stay in the European economy** (vs < 20 cents with a US hyperscaler, even when hosted in France). Timeline: PoCs completed, rollout starting at **Sephora and Louis Vuitton**, significant footprint targeted within **12-18 months**. Scaleway's stated mission: focus on **IaaS/PaaS** (no verticalization such as office productivity software), relying on a partner ecosystem (sovereign applications, European chipsets and servers). Scaleway's **Nvidia GPU / AI** offering is **not planned in the short term** but remains open (open source models for autonomy + economic performance).
**Bertrand** — journaliste / présentateur du média **République** (partenaire de VivaTech) · conduit l'entretien. **Damien Lucas** — CEO de **Scaleway**. **Franck Le Moal** — Global Technical Officer du groupe **LVMH**.
An arXiv paper (cs.SE) by Martin Monperrus arguing a radical thesis for the SDLC: coding agents have crossed a threshold of capability such that **human code review is no longer a necessary component** of a quality pipeline. Two claims: (1) autonomous LLM-based systems achieve all the goals of review (defect detection, quality, compliance) at lower cost and higher throughput; (2) the hybrid model "the agent writes, the human reviews" is untenable — it does not ensure real quality and does not scale with AI velocity, creating a "false sense of security". Monperrus contrasts inspection de Fagan (1976) with a **multi-agent adversarial verification pipeline** (generator agent + independent reviewer agents + tests/formal methods + vote-based consensus). The human refocuses on the spec, architectural trade-offs, approval of critical domains, and edge cases. Recommendations: pilot first on low-risk components, measure agent vs. human, make rejection decisions explicit.
Philippe Ensarguet (Orange) argues that fifty years of design patterns form a continuous lineage: at a time when AI commoditizes code and breaks the traditional way architects are trained, "pattern literacy" (reading a system through its invariant forces) becomes the durable skill to teach — as a grammar, not as catalogues.
Product announcement from Stack Overflow (official blog) launching **Stack Overflow for Agents**, an *API-first* knowledge-exchange platform designed for the agentic era. Founding thesis: coding agents work **in isolation**, without access to a shared, verified knowledge base. Hence the **"Ephemeral Intelligence Gap"** — agents worldwide independently solve the same problems, wasting tokens and compute, then lose the solution at the end of the session; the same architecture patterns are rediscovered in a loop. Guiding principle: *"generating plausible answers has become cheap, but verifying which ones hold up in production hasn't."* Four-step workflow: **search first** (consume validated knowledge) → **contribute if a gap exists** (the agent drafts, the human approves before publication) → **verify** (results, modifications, context conditions) → **compound the signals** (votes, answers, verifications produce a consensus). Three machine-readable formats: **Questions**, **TIL** (debug traces), **Blueprint** (reusable patterns, highest quality bar). Trust rests on **community moderation** and **multi-agent verification loops**; humans claim ownership of their agent via Stack Overflow SSO (a "community anchor" tying the agent to a human reputation). Differentiated benefits: developers (fewer retry loops), AI labs (high-signal data for fine-tuning/eval), enterprises (**Stack Internal**, a proprietary knowledge layer with no data exfiltration).
#Stack Overflow for Agents#coding agents#knowledge base
Anthropic launches Claude Fable 5 (a Mythos-class model made safe for general use) and Claude Mythos 5 (the same model, with guardrails lifted, restricted to cyberdefenders via Project Glasswing): state-of-the-art performance in software engineering, vision, long-context memory, and life sciences.
In-depth technical guide (Lushbinary agency blog) on **Loop Engineering**: designing the systems that drive coding agents in a loop, rather than prompting them manually. Covers the lineage prompt → context → loop engineering, the Ralph technique (Geoffrey Huntley), the **five building blocks + memory** of a loop, their implementation in Claude Code and OpenAI Codex, writing verifiable stop conditions, an adoption maturity scale, and the risks that worsen as loops grow more sophisticated. Domain: agentic software engineering, coding agents, harness/orchestration.
Guide by Augment Code (Paula Hingel) describing how AI agents are restructuring the software development lifecycle (SDLC), stage by stage. Thesis: AI produces **higher throughput at some stages and higher instability risk at others** — a symptom of uneven adoption without redrawing review boundaries. Draws on **DORA 2025**: AI adoption correlates positively with delivery throughput and product performance, but **negatively with stability**. Six stages revisited (Requirements, Design/Architecture, Implementation, Testing/QA, Deployment, Maintenance), three major risks (erosion of the junior pipeline, **circular validation** of AI-generated tests, governance gaps at scale) and three emerging roles (**Intent Engineering**, Agentic DevOps, AI Governance/Assurance). Actionable recommendations: audit one stage before scaling, stress-test governance, make the **specification** central, define explicit rollback policies, redesign the junior role around review.
#SDLC#software development lifecycle#coding agents
Sunday tinkering post by **Mark Dembo** (Head of Solutions, Developer Platform & AI at **Cloudflare**) published on **June 7, 2026** on his personal blog. **Narrative**: inspired by **Steve Ruiz**, the author buys a small **M5Stack Stick 3** device (~€30) and, taking advantage of the release of **Opus 4.8**, builds himself a **DIY AI agent** "out of pure curiosity, with no goal." **Iteration 1 (45 min)**: he throws the device's documentation at **Claude Code**, which generates Python scripts (~200 LOC, *"zero blast radius"*) displaying the weather in Munich, then several cities; a **Cloudflare Workers + Workers AI backend** adds **text-to-speech (TTS)**, **push-to-talk** (speech-to-text), and a central **small LLM** to answer questions. **Iteration 2 (a real agent)**: switching REST endpoints to **WebSocket** transport via the **Cloudflare Agents SDK** + **Dynamic Worker execution** → the ***"Code Mode"*** pattern (the agent writes and executes code to accomplish its task). The agent then answers public-data questions (11! = factorial, the Champions League winner via `fetch()` on Wikipedia, the weather in any city). **Iteration 3 (real powers)**: connecting to **Todoist** via an **MCP OAuth** flow → 50 tools at once, hence two problems: **context bloat** and **real damage risk**. The fix draws on Cloudflare's **MCP Server Portal** + Claude connector settings: per tool, **Always allow / Ask for approval / Disable** (*Disabled* tools never enter the context; an **LLM classifier** accepts only distinct "allow" grants and **defaults to deny**). **Stated posture**: reducing his role to ***"idea generator, executor and judge"*** (and rarely technical guide), a "human-in-the-loop" flow he considers not very *"2026"* (copy-pasting into UIFlow). **What he did NOT do**: no latency/streaming optimization, no optimistic LLM calls, no evals, ***"I did not even look at the code once."*** **Wonder**: €30 + one Anthropic session window + a few cents of Cloudflare inference → an object that listens and speaks, driven in natural language; *"the true unlock is how accessible it is."* Sharp contrast with [[thomas-pragdave-failing-faster-code-rot-ai-velocity-2026-06-06]] (here *"zero blast radius"* justifies never looking at the code); concretely illustrates *Code Mode* / *"the agent just writing and executing code,"* the **MCP** pattern ([[claude-skills-bigger-than-mcp-willison-2025-10-16]]), *Ask for approval*-style tool governance (uber-engineering-agent-identity-crisis-zero-trust-spire-2026-05-21), and the *systems around the model* doctrine from dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28.
#BYO agent#bring your own AI#tinkering
**Mark Dembo** (@darkmembo / @mdembo) · **Head of Solutions – Developer Platform & AI** chez **Cloudflare** (auparavant auteur sur le blog Cloudflare). Billet personnel publié sur son blog *markpauldembo.com* le **7 juin 2026** (description : *« Thoughts about tinkering on a Sunday »*).
Post by **David "Pragdave" Thomas** (co-author of *The Pragmatic Programmer*, signatory of the Agile Manifesto) published on **June 6, 2026** on his Substack newsletter. **Thesis**: AI does not abolish code degradation, it **accelerates** it. While adding features to a small personal animation/graphics project with **Claude**, the author moves from initial enthusiasm (oklch, SVG animations shipped in a week) to permanent regression cycles by week two. Striking formulation: what teams took ***"18 months, or even more"*** to rot, he reached in ***"18 hours spread over five evenings."*** **Root cause**: the abandonment of **code hygiene** (massive duplication, local solutions to systemic problems, over-conditioning, proliferation of special cases). **Behavioral diagnosis**: LLMs optimize for user engagement and satisfaction (*"That's a great idea, Dave!"*) rather than durability — they are ***"puppy-dog junior developers, eager to please but quite messy to have around"*** who constantly propose new features and discourage refactoring. **Central insight**: any non-developer can succeed at the *"first week"* of AI coding; it is **professional judgment** — knowing when to stop to refactor — that separates the experienced engineer from the novice. **Epigraph** (Gordon Bell): *"Every big computing disaster has come from taking too many ideas and putting them in one place."* **Conclusion**: ***"It's still just programming"*** — untended code rots, whether in 18 hours or 18 months; everything learned about good code still holds, the effect is simply **amplified**. Converges with the *"the faster execution gets, the stricter the framework must be"* doctrine of [[rafal-wenvision-ingenierie-logicielle-ere-ia-tout-change-rien-ne-change-2026-06-01]], the *"AI-assisted development is a trap without continuous delivery"* of [[farley-continuous-delivery-ai-assisted-development-trap-2026-05-13]], and the *"AI moves bottlenecks, it doesn't eliminate them"* of dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28; a craftsmanship counterpoint to vibe coding from karpathy-vibe-coding-agentic-engineering-software-3-0-2026-04-29.
#code hygiene#code rot#code degradation
**David Thomas** (alias **« Pragdave »**) · co-auteur avec Andy Hunt de *The Pragmatic Programmer* (1999, éd. 20e anniversaire 2019) · co-fondateur de **The Pragmatic Bookshelf** et l'un des **17 signataires du Manifeste Agile** (2001). Figure historique du *software craftsmanship*. Billet publié le **6 juin 2026** sur sa newsletter Substack *articles.pragdave.me*.
Analysis by **Olivier Rafal** for **WeNvision** (French consulting firm), published on **June 4, 2026** (~4 min read), commenting on the launch of the **Tokenomics Foundation** by the **Linux Foundation** (announced June 3, in partnership with the **FinOps Foundation**), which he sees as the official opening of **the era of "FinOps for AI."** **Pivot thesis**: AI has transformed the economics of software development; the **token** has become *"the new unit of measurement for technology spending,"* mirroring the cloud of the 2010s (**recurring and variable** costs requiring active management), hence the shift by providers from flat-rate pricing to **token-based billing**. **Scale (urgency)**: *"According to Goldman Sachs, global token usage is expected to increase 24-fold by 2030, reaching 120 quadrillion tokens per month"* — an order of magnitude that moves token efficiency from a *"technical detail"* to a **boardroom** topic. Quote from **J.R. Storment** (founder of the FinOps Foundation): *"Token costs and efficiency have become a CEO-level concern, not a technical footnote."* **Transparency/standardization problem**: current AI pricing is not comparable (input tokens / caching systems / output differ from one model to another) → the Tokenomics Foundation aims to **extend the open-source FOCUS specification** to provide a **common language** for purchasing and comparison. **Rafal's central message (beyond cost)**: *"The point of FinOps is not so much to cut costs as to optimize efficiency"* — the real metric is **AI cost relative to business impact** (*time to market, quality, features, eco-design*). **Limits of standards alone**: technical norms are not enough; the **Target Operating Model must be rethought** (teams, processes, data culture, business alignment); Americans are already announcing *"the end of double-pizza teams in favor of sandwich teams."* **Warning marker**: *"an AI-boosted SDLC will merely […] amplify the problems and just help you go faster… into the wall"* (absent organizational foundations). **Foundation sponsors cited**: Accenture, Booking.com, Google Cloud, Microsoft, IBM, Salesforce. **WeNvision's offer**: *"co-build a roadmap, rethink the operating model for the agentic era, and establish the financial governance that has become indispensable."* **French-language reading, aimed at executives/transformation leaders**, of the fiche [[tokenomics-foundation-linux-finops-token-economics-about-2026-06-03]]; converges with the agentic FinOps cluster [[finops-foundation-finops-for-ai-overview-2026-02-17]], finout-finops-ai-agents-four-step-allocation-framework-2026-04-27, gupta-token-budget-wars-marginal-token-utility-2026-05-28 (token→outcome, value > volume).
#Tokenomics Foundation#FinOps for AI#FinOps for AI
**Olivier Rafal** · pour **WeNvision** (cabinet de conseil français — bureaux à Paris, Lille, Strasbourg, Bordeaux, Nantes, Toulouse, Belgique, Luxembourg). Olivier Rafal écrit en analyste/conseil familier des préoccupations de comité de direction (ancien analyste IT, profil conseil-transformation). Publié le **4 juin 2026**.
Engineering write-up from Anthropic's **Data Science & Data Engineering** team (Chen Chang, Clement Peng, Justin Leder, Johanne Jiao, Josh Cherry) published on **June 3, 2026** on the Anthropic blog (*Enterprise AI* category, focus on **Claude Code**). **Headline result**: ***"95% of business analytics queries are automated by Claude, with ~95% accuracy in aggregate"*** (up to **~99%** in certain domains). **Core problem**: analytics is **not** code — *"there's often only a single correct answer using a single correct source"* — it requires **mapping a user question to precise, up-to-date entities** in the data model. Three **failure modes**: (1) **concept↔entity ambiguity** (e.g. *"active users"*: which actions? exclude fraudsters? which window?); (2) **staleness** (assets and the agent's knowledge become *"subtly wrong"*); (3) **retrieval failure** (*"80% of failed queries had the information present in the corpus"* but unfindable). **Solution = a 4-layer "agentic analytics stack"**: (L1) **Data foundations** — dimensional modeling, **canonical datasets** *"single source-of-truth"*, metadata *"as a first-class product"*, integrity via CI/CD; (L2) **Sources of truth** in decreasing order of trust — **semantic layer** (the agent is *"structurally required (by skill instruction) to leverage the semantic layer first"*), lineage graph, **query corpus** (distilled into structured docs, **not** raw retrieval), business context (knowledge graph: roadmaps, decision logs, org); (L3) **Skills** — the decisive lever: ***"without skills … didn't exceed 21% … Adding skills gets these numbers consistently above 95%"***; structured **in pairs** (*Knowledge skill* = router to ~30 reference files; *Unbook skill* = senior analyst workflow: clarify → find sources → execute → **adversarial review**); **colocated** maintenance (*"a code-review hook flags any reporting-model change that doesn't touch a skill file"* → **~90% of data PRs include a skill change**); (L4) **Validation** — offline evals (threshold ~90% to launch an agent, target ~100%), **ablation testing** (notable negative result: raw grep across thousands of SQL files → accuracy moves *"less than a point"*), online (adversarial review: **+6% accuracy, +32% tokens, +72% latency**), **provenance footers** (source tier + freshness + ownership), **active correction harvesting** (scheduled agents scanning channels to draft markdown fixes). **Strategic insight**: *"documentation generated, definitions owned by humans"* — letting the LLM **define** metrics was *"net-negative"*. **Minimal starting point**: a handful of canonical datasets + a few dozen evals + a *thin knowledge skill* capture *"most of the upside"*. Strongly converges with [[shihipar-claude-code-lessons-building-skills-2026-06-03]] (skills = folders, Gotchas, hooks), the *systems around the model* doctrine of [[dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28]], the **semantic layer / ontology** of talisman-modern-data-101-ontology-pipeline-refresh-2026-05-04 and seale-semantic-agent-model-harness-ontology-data-2026-04-17, the *context development lifecycle* of debois-tessl-context-development-lifecycle-ai-coding-agents-2026-02-19, and the UDA/knowledge graph of netflix-uda-unified-data-architecture-knowledge-graph-2025-06-12.
#self-service analytics#agentic data analytics#Claude Code
**Chen Chang · Clement Peng · Justin Leder · Johanne Jiao · Josh Cherry** — équipe **Data Science & Data Engineering d'Anthropic**. Article publié le **3 juin 2026** sur le blog Anthropic (claude.com/blog) · catégorie *Enterprise AI* · ~5 min de lecture.
Blog post from **Anthropic / claude.com** by **Thariq Shihipar** (Member of Technical Staff, Claude Code team), published on **June 3, 2026**, which distills Anthropic's **internal experience** on designing and using **Skills**. **Framing thesis**: a Skill is not a simple markdown file but a **folder** (instructions + scripts + resources + config + hooks) that the agent **discovers and manipulates**; *« You should think of the entire file system as a form of context engineering and progressive disclosure. »* The article makes two structuring contributions. **(A) A taxonomy of 9 skill categories** observed at Anthropic: (1) **Library/API Reference** (docs for internal libs/CLIs with *gotchas* — e.g. `billing-lib`, `internal-platform-cli`, `sandbox-proxy`); (2) **Product Verification** (testing/verification via Playwright or tmux — `signup-flow-driver`, `checkout-verifier`, `tmux-cli-driver`); (3) **Data Fetching & Analysis** (access to data/monitoring stacks — `funnel-query`, `cohort-compare`, `grafana`, `datadog`); (4) **Business Process Automation** (repetitive workflows — `standup-post`, `weekly-recap`, `create-<ticket>-ticket`); (5) **Code Scaffolding** (framework boilerplate — `new-migration`, `create-app`); (6) **Code Quality & Review** (`adversarial-review`, `code-style`, `testing-practices`); (7) **CI/CD & Deployment** (`babysit-pr`, `deploy-<service>`, `cherry-pick-prod`); (8) **Runbooks** (multi-tool diagnostics — `<service>-debugging`, `oncall-runner`, `log-correlator`); (9) **Infrastructure Operations** (maintenance with guardrails — `<resource>-orphans`, `cost-investigation`). **(B) A set of best practices**: don't restate the obvious (*« Claude already knows how to code and can read your codebase »* → target what **contradicts default behavior**); polish the **Gotchas section** (*« the highest-signal content in any skill »*); **progressive disclosure** via the file tree (point to reference files depending on the situation rather than loading everything upfront); **descriptions written for the model** (*« the description field is not a summary, it's a description of when to trigger this skill »*); **setup flows** (config in `config.json`, otherwise prompt via `AskUserQuestion`); **persistent memory** (append-only logs / JSON via the `${CLAUDE_PLUGIN_DATA}` variable); **helper scripts** (*« lets Claude spend its turns on composition… rather than reconstructing boilerplate »*); **hooks conditionnels** (enabled only for the duration of the skill — e.g. a security hook blocking destructive commands). **Distribution at Anthropic**: skills are stored in `./.claude/skills`, informally shared via Slack in a sandbox folder, then promoted via **PR** to the internal **marketplace** once they gain traction; **usage measurement** via a **hook PreToolUse** that logs invocations (revealing popular skills versus underused ones). Direct follow-up to the fiche [[shihipar-claude-code-html-unreasonable-effectiveness-markdown-2026-05-10]] (same author) and a concrete complement to the Skills fiches by Anthropic/Willison/Vincent and to *harness engineering*.
#skills#Claude Code#Anthropic
**Thariq Shihipar** (Member of Technical Staff chez Anthropic, équipe **Claude Code** ; @trq212 / @trq sur X, thariqs.github.io) · pour le blog **claude.com**. Même auteur que la fiche *Using Claude Code: The Unreasonable Effectiveness of HTML* (2026-05-10). Publié le **3 juin 2026**.
**About** page of the **tokeneconomics.com** website, presenting the **Tokenomics Foundation** — a **Linux Foundation** project announced on **June 3, 2026**, operated in **close partnership with the FinOps Foundation**. **Stated mission**: *"establish open industry standards, benchmarks, and best practices for the economics of AI infrastructure"* — linking **production, consumption, and monetization** of tokens to **business value**. **Framing definition of tokenomics**: *"Tokenomics is not just about the cost of tokens, it's about the entire layer of AI that they drive from production, to consumption to monetization"* — that is, **the entire economic layer of AI**, from infrastructure cost to model selection to value optimization. **Phase thesis**: early AI adoption prioritized **capability**; the current phase is shifting toward **efficiency and value**, which requires systematic cost management and **visibility**. **5 founding principles**: (1) ***"Efficiency is a design choice. AI cost is shaped by architecture, not just usage"***; (2) ***"Bigger is not always better. The best AI system is not always the one using the most expensive model"*** (right-tool / routing); (3) ***"Visibility comes before optimisation. Teams cannot manage what they cannot see"***; (4) ***"Value matters more than volume. More tokens, more calls, and more automation do not automatically mean better outcomes"***; (5) ***"Open knowledge benefits everyone"*** (shared standards, community learning, transparency). **Governance**: a **Governing Board** (industry direction + fund deployment) and a **Technical Committee** (open specifications + benchmarks). **Deliverables**: extension of the **FOCUS specification** (FinOps), open specs, benchmarks, shared frameworks and metrics. **Target audience**: CAIO, CTO, CIO, CFO, engineers, product teams, FinOps practitioners, researchers, startups, enterprises, public sector. **Stated goal**: moving organizations *"from experimental AI adoption to sustainable AI operations"* by extending the discipline of **variable technology spend** into the token era. **Relevance to this watch**: institutionalization/standardization of **agentic FinOps** at an industry-foundation level — directly converges with the fiches [[finops-foundation-finops-for-ai-overview-2026-02-17]], [[finout-finops-ai-agents-four-step-allocation-framework-2026-04-27]], orq-ai-finops-ai-agents-cost-per-outcome-hosseini-2026-04-15, gupta-token-budget-wars-marginal-token-utility-2026-05-28 (allocation layer, token-to-outcome) and with the **token → outcome** shift (Salesforce/Tallapragada, Sierra/Greenwald). The 5 principles map exactly onto levers already captured: architecture > usage, **Haiku/Sonnet/Opus routing**, observability before optimization, value ≠ volume.
#Tokenomics Foundation#tokenomics#token economics
**Tokenomics Foundation** (entité collective, projet de **The Linux Foundation**, en partenariat avec la **FinOps Foundation**). Page institutionnelle *About* — **aucun auteur individuel nommé**. Annonce datée du **3 juin 2026**.
On the eve of SpaceX's record IPO (targeted valuation of ~$1.75 to 1.8 trillion), The New York Times publishes an interactive analysis of Elon Musk's track record of public promises. Across more than 600 dated, quantified commitments (statements, posts, investor calls), only ~19% were kept on time, if ever. The rate deteriorates over time: ~75% kept in 2015, less than 50% in 2020. Mars, the robotaxi, and full autonomy account for most of the repeated and postponed targets. The piece links this track record to the SpaceX prospectus, which now bets on AI (xAI merged in) and itself acknowledges that the timeline for its major undertakings is undeterminable.
Guide from the media outlet **Every** (every.to/guides) published on **June 2, 2026**, co-signed by **Mike Taylor, Laura Entis and Claude**, proposing an **8-level maturity scale for AI adoption**. **Pivot thesis**: AI adoption **is not a race toward maximum sophistication** — ***« a higher level isn't necessarily better »*** ; one must identify the level that **matches one's own workflow and level of trust**, then regularly reassess whether moving up a notch adds **real value**. ***« The best way to find value in AI is to use it in a way that fits your work. »*** **Structuring axis**: at each level, *« you delegate more of your work to—and place more trust in—the AI »* (increasing delegation + trust). **The 8 levels**: **(1) Chatbot** — conversational interface with no embedded context (ChatGPT, Claude, Gemini); **(2) Copilot** — AI embedded in the workspace with access to the current file (Cursor, Claude in Excel, Gemini in Docs); **(3) Agent** — reactive system that executes step-by-step while requesting approval (Cowork, Codex); **(4) Autopilot** — one describes the **outcome** and the agent executes autonomously, review of the **final result** only (Lovable, Codex, Claude Code; tied to *vibe coding*); **(5) Workflows** — engineers building **harnesses** around agents (planning, review, confidence checks, guardrails; Compound engineering, Claude Workflows, Copilot AI Studio; shift from one-shot vibe coding → **agentic engineering**); **(6) Assistant** — **proactive, always-on** agents that monitor a domain and surface information without being prompted (OpenClaw, Hermes Agent, Claude Managed Agents; e.g. `heartbeat.md` every 30 minutes); **(7) Multi-agent** — simultaneous management of **several long-running agents** with distinct roles (Claude Managed Agents, OpenClaw, Codex Goals; *« firmly in senior engineering territory »*); **(8) Orchestrator** — an **agent manager** directs a team of sub-agents (planning, delegation, monitoring, consolidation; Gas Town, Paperclip, Symphony/OpenAI; *« highly experimental »* — even frontier engineers themselves hold this role). **Sweet spots by role**: **knowledge workers** typically operate between levels **1-4**, **engineers** between **5-8**. **Canonical parallel of intern onboarding**: *« Expect to put in a similar amount of effort with your agents before you can trust them… at the next level of autonomy »* ; and the marker phrase ***« You wouldn't brag that you had eight interns working overnight on a key project, and you hadn't checked their output. »*** The right level depends on **4 criteria**: output quality, cost, reliability (trustworthiness), stakes of failure; and **model capability** progressively shifts the "safe" level of autonomy. A framework directly usable to structure an **adoption doctrine** on the consulting side. Convergence with *systems around the model* (Dropbox/Okumura), *harness engineering* (Böckeler, Lattice, Wescale), Karpathy (vibe coding → agentic engineering), Cherny (/loop + Routines), and the *agent manager* doctrine (BFM/Girard).
#AI adoption#maturity scale#eight levels
**Mike Taylor** · **Laura Entis** et **Claude** (co-auteurs déclarés) · pour **Every** (every.to) · rubrique *Guides*. Mike Taylor est un auteur connu sur les sujets prompt/AI (co-auteur de *Prompt Engineering for Generative AI*) ; Laura Entis est journaliste/éditrice. La co-signature explicite de **Claude** comme auteur fait partie du positionnement éditorial d'Every (entreprise AI-native). Publié le **2 juin 2026**.
Op-ed by **Olivier Rafal** (Consulting Director Strategy, **WeNvision** — **SFEIR** group; former editor-in-chief of *Le Monde Informatique*) published on **June 1, 2026** on **CIO-Online**, structured around a **paradox**: in the age of AI, software engineering **changes everything… and nothing changes**. **What changes is the operating model.** Roles are redefined: the **Product Owner** shifts from backlog breakdown to **generating context usable by AI**; the **developer** shifts from writing code to **framing, steering, and reviewing** agent execution; **QA** gains the ability to define **expected proof** upfront. Team structure shifts from *"double pizza teams"* (hand-off chains of ~8 people) to ***"sandwich teams"***: a **tight pairing of a business expert and a tech lead, both AI-augmented**, with other skills in support. Internal **Sfeir** figure: *"this pair now drives roughly 80% of the production chain,"* the remaining ~20% (architecture, data governance, security) being centralized. Pivot quote: ***"The issue isn't a tooling issue, it's an operating-model issue."*** **What doesn't change is the discipline of the cycle.** The **SDLC** phases (define → build → verify → deploy → maintain) remain identical and non-negotiable; AI removes none of them, it **intensifies** them: ***"all the slack that human pacing used to absorb, however imperfectly, becomes, at AI speed, industrial-grade defects"*** (an amateur-vs-professional sports metaphor). Hence **three inviolable *gates*** (human control): **specification, planning, delivery review**; validation **by proof** (not by AI's own assertions); **systematic capitalization** (each cycle feeds the next) → measured result: **−30% correction iterations after ~10 cycles**. Principle: ***"the faster the execution, the stricter the framework must be."*** Concepts invoked: **harness** (agentic rules adapted to context), **vibe-coding** judged **untenable in the enterprise**. **Third pillar = governance, FinOps & value-driven management**: **variable and recurring** AI costs (~**€10/hour** per augmented role), shift from flat-fee licensing to usage-based billing (a parallel with cloud in the 2010s); **FinOps** does not aim to cut costs but to *"optimize tool efficiency"* (cost relative to value); aligning **business metrics** upfront (time-to-market, features, performance, eco-design). **Conclusion**: acceleration makes the fundamentals **non-negotiable**; the challenge is **organizational and cultural**, not technological — without securing the business relationship and collective discipline, an AI-powered SDLC only **amplifies the problems** (driving into the wall faster). Extends the WeNvision doctrine of [[rafal-wenvision-ia-generative-produit-techno-pas-projet-2024-02-23]] and [[rafal-wenvision-tokenomics-foundation-finops-ia-2026-06-04]]; converges with *systems around the model* dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28, *harness engineering* osmani-agent-harness-engineering-2026-04-19, agentic Salesforce, and the *agent manager* debate (BFM/Girard, SFEIR).
**Olivier Rafal** · *Consulting Director Strategy* chez **WeNvision** (groupe **SFEIR**). Ancien **rédacteur en chef du *Monde Informatique*** · et auparavant consultant analyste du marché IT (~10 ans). Tribune publiée dans la rubrique *Tribune* de **CIO-Online**. Publié le **1er juin 2026**.
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.
Short article (**8 pages**, 4 exhibits) from **McKinsey Technology**, authored by **Jared Moon** (senior partner, London), **Rory Walsh** and **Vito Di Leo** (partners, Dublin and Zurich), with **Adam Thelwall**, published in **May 2026**. The authors report productivity gains of **×3 to ×5** with a **60% reduction** in team size at several companies, and attribute them to redesigning the operating model, not to agent deployment alone. Four levers: (1) the **24-hour sprint**, with a night shift of agents (16h) and a human day shift (8h); (2) automating the **handoffs** between requirements, design and code, which they say account for **70% of tech spend** against 30% for deployment; (3) a **knowledge infrastructure** of domain-specific graphs, queried by an agent « bibliothécaire »; (4) resizing teams and the portfolio. On the graph: *« this should not begin with a grand, top-down ontology effort »*. The team figures are presented as illustrative, drawn from the firm's "experience and observation." Extends McKinsey's November 2025 presentation on agent-driven software delivery ([[harrison-maniar-mckinsey-reshaping-software-delivery-agents-2025-11-23]]).
#McKinsey#agentic SDLC#operating model
Jared Moon (senior partner) · Rory Walsh · Vito Di Leo (partners) · avec Adam Thelwall (associate partner) — McKinsey & Company
Blog post by **Pasquale Pillitteri** (software engineer, Palermo) published on **May 29, 2026** (FR version), 18-minute read, *Claude Code & Anthropic* section. **Pivot thesis**: *« Claude Opus 4.8 is the most powerful SEO model of 2026, but almost everyone uses it wrong »* — not a model problem but a **system** problem. The golden rule: ***« strategy is a whiteboard, production is an assembly line »*** — SEO must be **split into two distinct phases**, and mixing them is *« the fastest way to waste a model that costs five dollars per million input tokens and twenty-five for output »*. **Model context**: Opus 4.8 released on **May 28, 2026** (41 days after Opus 4.7), **1M-token** context, **GraphWalks Long-Context F1 at 1M: 40.3% → 68.1%**, **SWE-bench Verified 88.6%**, **USAMO 2026 96.7%** (+27.4 pts), **HLE with tool 57.9%**, unchanged price **$5/$25** per M tokens, **Fast Mode 2.5× at $10/$50**, four **effort levels** (Low, High, Extra, Max). **The central anti-pattern** = *« the giant conversation »* / **context drift**: mixing strategy, keyword research, competitive analysis and writing in a single chat produces a *« mush of contradictory intentions »* → the model slides toward **generic best practices** ("holistic optimization", "strategic approach") instead of data-anchored content. **Phase 1 — Strategy (whiteboard, visual UI, one-off)**: dashboard / Google Sheet / Claude.ai canvas to decide while looking at the data together. **3 plays**: (a) **classified keyword research** (table of volume / difficulty 0-100 / intent / business potential / priority = volume÷difficulty×business weight); (b) **visual competitive analysis** (topic-coverage matrix, gaps); (c) **phased roadmap** (quick wins M1-2 / medium term M3-6 / pillar pages M7-12). **Extra/Max** mode is justified here (*« one right strategic decision is worth a thousand well-written pages on the wrong keywords »*). 3 closed artifacts saved to Notion/Drive. **Phase 2 — Production (assembly line, Opus 4.8 + MCP)**: the model shifts from strategist to **execution machine**; every decision **anchored to live data** via the **Model Context Protocol**. **Minimum MCP stack**: **GSC MCP** (AminForou/mcp-gsc, 500+ stars), **official Ahrefs MCP** (98 stars), **GA4 MCP**; the `modelcontextprotocol/servers` repo = **86,440 stars**, **10,000+ active servers**, 97M SDK downloads/month. Setup ~35 min, monthly refresh ~20 min. **Weekly loop**: a single prompt pulls live data, builds the brief (top 10 SERP + GSC + Ahrefs), derives H2/H3, writes, checks density, suggests titles → **+45% productivity**, draft in **6-12 min** (explicit reference to **Ryan Law / Ahrefs content engineering**, 23 skills). Mentions Anthropic's **Dynamic Workflows** (up to 1,000 subagents). **4 common mistakes**: (1) not checking the numbers (spot-check mandatory, *trust & verify*); (2) fully replacing Semrush/Ahrefs (MCP is a **layer on top**, not a substitute); (3) ignoring the **paid-organic content gap** (education client case: **2,742 wasted terms / 351 opportunities** identified in 90 s); (4) using Opus 4.8 where **Haiku 4.5** suffices (meta descriptions, alt text). **Cost**: $1-3 per 2,500-word article. **Sonnet 4.6** suffices for recurring production, Opus 4.8 reserved for strategy. SEO-optimized and self-referential article (the author writes about SEO in content itself designed to rank for "Opus 4.8 SEO"). Direct convergence with **Ryan Law/Ahrefs** (cited), **systems around the model** (Dropbox/Okumura), **skills-over-prompts** (Lattice), Haiku/Sonnet/Opus model routing (Gupta token-to-outcome).
#Claude Opus 4.8#AI SEO#two-phase workflow
**Pasquale Pillitteri** — Ingénieur informatique / développeur logiciel basé à **Palerme** (Italie) · certifié Innovation Manager UNI 11814:2021. Auteur d'un blog tech actif (rubrique *Claude Code & Anthropic*) · avec une newsletter hebdomadaire (~3,4k lecteurs). Article publié en version **FR** le **29 mai 2026** (lendemain de la sortie d'Opus 4.8).
Post from the **Dropbox Tech blog** (*culture* section), published on **May 28, 2026** by **Kazuaki Okumura** (Dropbox, role unspecified in the article), recapping a talk at the **DX Annual 2026** conference (developer productivity). **Pivot thesis**: engineering productivity must move beyond *code generation*. *« Accelerating code generation simply shifted some bottlenecks downstream »* — AI has massively increased code throughput, but *« the faster code moves, the more pressure it puts on review queues, CI systems, validation workflows, release coordination, and production operations »*. The real challenge is no longer writing code faster, but enabling the entire SDLC to **absorb, validate, and ship safely** a much larger volume. **From copilot to agent**: the first wave (code explanation, snippets, Q&A) operated *« as copilots alongside the engineer »*; the agent, by contrast, *« can take a scoped task, inspect the codebase, edit files, run tests, iterate on failures, and return an artifact for human review »* — with the engineer remaining *« accountable for intent, architecture, quality, and release decisions »* (more parallel work, more options, offloading repetitive execution). **Nova** = Dropbox's **internal** coding-agent platform: describe a task in natural language, execution in a controlled environment with codebase context. Canonical datapoint: ***« Nova's value comes less from the model itself than the systems surrounding it »*** (codebase context, internal practices, safe execution, workflow integration, human review); Nova accounts for **~1 in 12 PRs at Dropbox** today (adoption growing), and extends beyond features to **migrations, flaky-test remediation, bug investigation, dependency updates** (high-toil work). **Measuring product velocity, not code output**: *PR throughput*, a useful signal when coding velocity was the constraint, *« was no longer sufficient »*. A **4-stage** measurement model: ***Fuel*** (are AI tools being used?) → ***Adoption*** (how workflows are changing across teams) → ***Output*** (is AI contributing to production work?) → ***Impact*** (*« improving product velocity and reducing the time it takes to move from idea to customer value »*). Quality signals tracked: **code review turnaround time, first-run test pass rate, defect ratio, rework rate**. *« Quality and trust matter as much as speed »* — the core of the shift: *« moving from local activity metrics toward broader system outcomes »*. **Workflows have to evolve too**: this is *« not just a tooling shift »* but a change of **operating model** — the engineer's role shifts toward *« defining intent, mapping problems, reviewing generated changes, and making higher-context architectural and quality decisions »*. **Enablement** is as crucial as the tool itself (hands-on learning, hackathons, workflow spotlights, bootcamps, peer-led examples); adoption proceeds at varying speeds across teams; *« The goal is not to force every workflow through an agent »* — the goal is to make it *« useful, safe, measurable, and repeatable where it creates meaningful leverage »*. **What we learned**: ***« AI doesn't eliminate bottlenecks in software development, but it does move them »*** (downstream: review, validation, testing, release, prod ops) → optimizing the old bottleneck no longer creates the same leverage. *« The advantage will not come from access to the same foundation models everyone else can use. It will come from the systems built around those models: context, internal tooling, quality controls, and the workflows that connect them together. »* Pressure also builds **upstream** (product & design): structured specs, design clarity, sharper problem framing. Closing: ***« The future of engineering productivity will not be defined solely by who has the best models. It will be defined by who builds the best systems around them »***; *« The real challenge is no longer just generating more code, but building engineering systems that can reliably turn AI-assisted output into valuable experiences for our customers »*. Direct convergence with **Salesforce/Tallapragada** (Effective Output: measuring value, not volume; no speed/quality tradeoff), **Gupta** (token-to-outcome attribution, cost of a completed outcome), **DORA** (beyond throughput), and the shift of the KPI toward **system outcome** (idea→customer value).
**Kazuaki Okumura** — Dropbox (rôle non précisé dans l'article ; le billet reprend une intervention présentée à la conférence **DX Annual 2026** sur la productivité développeur, ce qui suggère un profil engineering leadership / platform, sans confirmation). Publié sur le **Dropbox Tech blog** (dropbox.tech) · rubrique *culture* · le **28 mai 2026**.