In episode #351 of If This Then Dev, Julien Lépine (CTO of AWS France) looks back at the AWS Summit Paris (April 1, 2026, ~10,000 attendees) and the transformation of the developer role. His angle: AWS is not merely a spectator but an actor in this change, driven by its own need — producing critical services at a dizzying scale (DynamoDB: >5,000 billion requests/hour; the October 20, 2025 outage that took Fortnite offline outside Europe).
Central proof point: the redevelopment of Amazon Bedrock, AWS's agentic core. Estimated by Anthony Ligori (Distinguished Engineer) at 30 developers and 18 months, it was completed by 6 people in 72 days thanks to an agentic platform — code entirely generated by AI, largely reviewed, without any vibe coding given it is a critical production platform. As a result, AWS is standardizing internally on Kiro (IDE + CLI, running on Claude Sonnet/Opus, announced by Matt Garman at re:Invent) for ~30,000 developers, backed by a community (a Slack channel with 30,000 members, summarized every evening by AI) and shared ADRs.
The central debate is about value: if one can "generate 100,000 lines of code per day," do best practices still matter? Lépine cites Kent Beck ("99% of my value became useless, but the remaining 1% multiplied by 1000"): value shifts toward understanding context and architectural trade-offs. Good practices (security, the maintainability principles of the Well-Architected Framework, rejecting over-engineering) remain, but the challenge becomes keeping control without reviewing everything: formal TLA+ modeling guaranteeing invariants, deterministic and mathematically proven Raisonnement automatisé to bound agents, with AI checking code ↔ model divergence.
On accountability, the position is clear-cut: "it is not the agent's responsibility, it is the responsibility of the person operating it" — a culture of blameless post-mortem and mechanism. One incident (an agent with excessive permissions) led not to a shutdown but to new guardrails: any change impacting production, whether by a human or an agent, must be reviewed beforehand. Regulated industries (healthcare, defense, legal) adopt AI faster thanks to their existing data classification and their auditability.
On the organizational side: AI DLC replaces sprints with multiple daily Bolts, AI absorbs detailed specs, PM/PO/Scrum Masters gain superpowers, and communication barriers fall. But cognitive overload looms: one client deliberately slowed its pace to protect its developers. Conclusion: empathy, context, and understanding become the key skills, and the line between tech and tech-adjacent roles is blurring.