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".
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*).
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**.