In February 2026, Andrej Karpathy triggered what the industry now calls the Breakpoint of software engineering. His assessment is unequivocal: the programming profession is undergoing radical « refactoring ». For the modern developer, the feeling of experiencing a « Skill Issue » has become chronic—not due to lack of talent, but because tools evolve faster than our mental frameworks. We must face the truth: code is no longer the output; it’s the residue. The challenge is no longer writing syntax, but mastering Agentic Engineering.
1. The Shipwreck of Pure Autonomy: The Devin Case
2025 buried the myth of the totally autonomous agent. The Devin case became a cautionary symbol of the costly « black box ». Despite the promises, real-world success rates on complex tasks (measured by SWE-bench) stagnated between 13.8% and 15%.
The massive rejection of Devin by engineering teams in 2026 stems not merely from technical failures, but from an architectural control deficit and unacceptable economic opacity. At $500/month per seat plus $2 per ACU (Agent Compute Unit), companies realized that blindly delegating to an AI that « charges ahead » without alerting human supervisors was financial suicide. The market is shifting toward structured control models like Intent, where developers validate each planning step.
💡 The insight — The problem isn’t the agent’s intelligence, but the absence of a control harness.
2. The « Harness » Outperforms the Model: Amazon Kiro’s Approach
A system’s intelligence no longer resides in the LLM’s raw power, but in its support infrastructure: the Harness. A mediocre model with rigorous execution harness will always outperform the largest model left to its own devices.
This agentic stack rests on four critical layers:
- Context: Semantic indexing (RAG) of hundreds of thousands of files.
- Planning: Decomposing intent into logical sub-tasks.
- Execution: Interacting with the world via MCP (Model Context Protocol) and Agent Hooks (automatic triggers on file events).
- Learning: Persistent memory that prevents error repetition.
The prime example of this rigor is Amazon Kiro. Unlike intuitive coding, Kiro enforces a « Spec-driven » flow: transforming prompts into structured requirements using EARS format (When X, the system shall Y), followed by visual design via Mermaid, before any line of code.
Sources : Andrej Karpathy - Breakpoint, Amazon Kiro, SWE-bench
3. The Toxicity of « Vibe Coding »: The 90-Day Wall
Vibe Coding — the practice of coding « by feel » through prompt iterations without architectural vision — delivers misleading initial euphoria. It’s a high-velocity drug that masks explosive technical debt. A major study on 8.1 million pull requests confirms that ungoverned AI adoption increases technical debt from 30% to 41%.
The cycle is ruthless:
Phase Symptom Day 1 Development speed multiplied by ten Day 30 Duplicated logic appears, coherent error handling disappears Day 90 The wall. Code becomes « hostile ». Modifying a minor function triggers bug cascades no one can resolve Dimension Vibe Coding (Initial) Long-Term Maintenance Structured Control (Intent/Kiro) Input Vague natural language Deep understanding Structured specifications (EARS) Quality « Happy path » only Systemic fragility Edge case coverage Control Speed illusion Refactoring wall Human validation at each step > ⚠️ The warning — Vibe Coding kills maintainability. It’s the fastest route to the Technical Debt Ramp.
4. Micro-societies of agents: The MiroFish Explosion
Innovation no longer requires armies of engineers. In just ten days, a student at China’s University of Posts and Telecommunications, Guo Hangjiang, built MiroFish. With $4 million in funding from Chen Tianqiao (30 million yuan), this project illustrates the radical democratization of technological power.
MiroFish uses the OASIS framework to create not a chatbot, but a massive social simulation. By creating thousands of agent personas with persistent memories (via Zep Cloud), the system produced a credible ending to the literary masterpiece Dream of the Red Chamber. This shift from « answering a question » to « problem-solving via simulation » marks the future of public opinion prediction and market analysis.
💡 What changes — We move from the « I ask a question » paradigm to the « I run a simulation » paradigm.
5. Don’t Build a Mega-Agent, Orchestrate a Team
The fatal mistake in 2026 is trying to create an omniscient agent. Context saturation inevitably leads to hallucination. Software survival depends on collaborative architecture patterns:
Parallel Pattern (Swarms)
Ideal for massive research and divergent data analysis. Multiple agents simultaneously explore different branches of a problem.
Sequential Pattern (Pipeline)
For rigorous production. Each step validates the previous before moving to the next: Research → Writing → QA.
Supervisor Pattern
The core of ASD (Agentic Software Development). A coordinator agent decomposes tasks, delegates to specialists, and handles error recovery. This supervisor transforms stochastic chaos into reliable engineering.
💡 The key point — The Mega-Agent is a myth. Orchestration is the reality.
Conclusion: Toward « Software for One »
The developer’s role has shifted. You no longer write code—you orchestrate intent. We’re entering the era of Software for One: the ability to generate unique applications, throwaway or permanent, meeting an instant need.
Code has become a commodity; intent architecture is your new added value. If you could orchestrate a team of 1000 agents to solve a complex problem tomorrow, what would be the first step in your specification? The answer to this question defines your future in this new era.
The question to ask — Are you a developer who writes code, or an architect who orchestrates intent?
Nicolas Dabène — Architect of AI-native e-commerce transition & developer of MCP Tools Plus for PrestaShop. Certified PrestaShop expert with over 15 years of experience.