Quick Answer
In May 2026, Google published a 51-page whitepaper called The New SDLC With Vibe Coding, authored by Addy Osmani (a Director at Google Cloud AI), Shubham Saboo, and Sokratis Kartakis. It argues that AI hasn't shortened the software development lifecycle, it has moved the bottleneck. Writing code is no longer the expensive part; specifying what "correct" means and verifying that the AI actually delivered it now is. The paper draws a spectrum from vibe coding (casual prompts, "does it seem to work?", fine for disposable prototypes) to agentic engineering (formal specs, automated evals, CI/CD gates, built for production systems), and the only thing that separates the two ends is how rigorously the output gets verified.
The Core Idea: It's a Spectrum, Not a Binary
Three points on the spectrum, as the paper frames them:
- Vibe Coding: Casual, natural-language prompts. Verification is "does it seem to work?" High risk. Best for disposable scripts, prototypes, and proofs of concept.
- Structured AI-Assisted: Detailed prompts and structural outlines. Verification is manual spot-checking. Medium risk.
- Agentic Engineering: Engineered, often machine-readable specifications. Verification runs through automated evals, CI/CD gates, and LLM judges. Low risk. Built for production-grade and enterprise systems.
The practical test the paper offers: when the agent produces something wrong, what catches it? If the answer is "me, when I happen to notice," that's vibe coding regardless of how sophisticated your prompts sound.
Agent = Model + Harness
The paper's second major idea is an equation: an agent is a model plus a harness, roughly 10% model, 90% harness. The harness is everything wrapped around the reasoning engine, instruction files, tool and MCP integrations, sandboxes, orchestration logic, guardrails, and observability. Most agent failures, examined honestly, are harness failures, not model failures.
In February 2026, LangChain rebuilt the harness around a coding agent while holding the model completely fixed, and lifted its score on Terminal-Bench 2.0 from 52.8% to 66.5%, moving the agent from outside the top 30 to the top 5 on a public leaderboard, without touching the model at all.
How the Software Development Lifecycle Actually Changes
| Phase | Before | With Agentic Engineering |
|---|---|---|
| Requirements | Handoff document | A conversation that produces a spec and a working prototype together |
| Implementation | Days to weeks | Minutes to hours |
| Testing | Manual review at the end | Automated evals and CI/CD gates running continuously |
| Review | Human only | AI does a first pass; humans keep judgment on design |
| Maintenance | Often avoided on risky legacy code | An agent that respects existing architecture can safely refactor previously risky code |
Reading the Paper's Numbers With Some Caution
Its headline adoption figures trace back to marketing-statistics aggregators rather than primary research, even though stronger primary sources exist: Stack Overflow's 2025 Developer Survey found just over half of professional developers use AI tools daily, and Google's own DORA 2025 report puts workplace AI adoption at roughly 90% of nearly 5,000 respondents. The paper's often-cited productivity range of 25-39% draws on vendor blog posts rather than controlled studies.
Why This Matters for Custom ERP and Manufacturing Software Work
This applies directly to work like customizing Odoo and Openbravo modules and building the data pipelines covered in our Data Engineer and AI/ML Engineer service lines. Telling a client "we vibe coded your payment module" should raise alarms; describing the same AI-assisted speed under test coverage, specs, and CI gates is a completely different, more defensible conversation.
Frequently Asked Questions
Who wrote Google's "The New SDLC With Vibe Coding" whitepaper?
Addy Osmani, a Director at Google Cloud AI, together with Shubham Saboo and Sokratis Kartakis, published on Kaggle in May 2026.
What's the actual difference between vibe coding and agentic engineering?
Verification: vibe coding checks only whether output "seems to work," while agentic engineering runs it through formal specs, automated evals, and CI/CD gates.
What does "Agent = Model + Harness" mean in practice?
Most of an AI agent's real-world performance comes from the surrounding system rather than the model itself, roughly 90% harness, 10% model.
Is vibe coding always a bad practice?
No, it's the right speed for prototypes and throwaway scripts. The risk is letting vibe-coded work drift into production without moving to proper verification.
For more details, contact us, message us on WhatsApp, or add us on LINE.