The new SDLC: what the Google paper actually says · Okane Land<br>Skip to content dark

The Study · Explainer<br>The new SDLC with vibe coding: what Google's paper actually says<br>Akira Sumi · Jul 26, 2026 · 9 min read · researched<br>In May 2026 Google published a 51-page whitepaper called The New SDLC With Vibe Coding, written by Addy Osmani, Shubham Saboo, and Sokratis Kartakis, and then taught it to over a million people through a free five-day course in June. Its argument in one line: the software lifecycle keeps its phases, loses its old bottleneck, and gains a new one. Writing code is no longer the expensive part. Specifying, verifying, and judging what the machine wrote is. We read the full paper, checked its numbers against their primary sources, and pulled out what it means for a builder working alone.

The short version

The paper’s core move is a spectrum. Vibe coding and agentic engineering are endpoints of one practice, and the position on the line is set by how much verification surrounds the AI’s output. The tools can be identical at both ends.

Its most useful equation is agent = model + harness. The paper puts the split at roughly 10% model and 90% harness, and the receipt behind that claim is real: LangChain moved a coding agent from outside the top 30 to the top 5 on a public benchmark without changing the model.

The lifecycle keeps its shape and changes its proportions. Implementation compresses from weeks to hours; requirements, architecture, and review stay human-paced. Specification quality is the new bottleneck, and tests plus evals become how you tell the AI what correct means.

Read its statistics with the flags on. The framework is sound, and the paper’s headline adoption numbers cite marketing aggregators rather than the primary surveys that actually exist. We traced each one below; some hold, some are softer.

For a solo builder, the six-step starting list is the payload. An AGENTS.md, one repetitive workflow turned into an agent, tests before generation, and a review pass on every line that ships.

The rest is the framework in detail, with the sources open.

What the paper is, and where to find it

The whitepaper is the first entry in a series Google shipped alongside its 5-Day AI Agents intensive, the free Kaggle course whose November 2025 edition reached more than 1.5 million learners. The paper itself is hosted on Kaggle, dated May 2026, 51 pages with 32 endnotes. Osmani, its lead author, published a condensed companion essay on O’Reilly Radar in July, which is the version most people have actually read.

The timing explains why the searches spiked. The term vibe coding is Andrej Karpathy’s, from February 2025, and it stretched within months to mean any AI-assisted coding at all. By April 2026 Karpathy himself drew a new line at Sequoia’s AI Ascent, introducing agentic engineering as the disciplined end of the practice: vibe coding raises the floor of who can build software, agentic engineering raises the ceiling of what professionals ship. The Google paper is the institutional version of that split, with a course attached.

The spectrum, which is the actual answer

The paper refuses the binary. Vibe coding and agentic engineering are endpoints on a spectrum, and the differentiator is stated plainly: what decides your position is how outputs get verified, and nothing else. A developer can vibe code and practice agentic engineering with the same agent in the same afternoon.

At the loose end, casual prompts, no reading of the generated code, and a verification standard of “does it seem to work.” The paper is comfortable with this mode where the code is disposable: prototypes, scripts, hackathons. The middle is where most working builders live, detailed prompts and manual spot-checks on features inside an established codebase. The far end is formal specs, automated test suites, CI/CD gates, and LLM judges, with humans reviewing architecture while the AI handles implementation detail.

Two things about this framing earn their keep. First, it gives you a clean answer to a question clients and CTOs are already asking; the paper notes that telling a CTO you vibe coded the payment system should raise alarms, while describing the same AI leverage under constraints and test coverage is a different conversation. Second, it puts the boundary inside your control. Verification is a budget you spend by the stakes of each task, the same supervised-beats-unattended split the agent research keeps finding. The paper’s own line is that without tests and evals together, the practice is always vibe coding, no matter how sophisticated the prompts.

An academic taxonomy published a year earlier drew nearly the same map from the outside, splitting conversational, human-in-the-loop building from goal-driven autonomous execution across twenty use cases. The convergence is a good sign the distinction is real rather than branding.

Agent = model + harness

The paper’s second framework is the one with a receipt...