<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification--14yfikzdn" -->

---
title: Google Drew a Line Between Vibe Coding and Agentic...
description: A referenced Google whitepaper (attributed to Osmani, Saboo, and Kartakis) argues that vibe coding and agentic engineering aren't fundamentally different tools...
canonical: https://daily.dev/posts/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification--14yfikzdn
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Google Drew a Line Between Vibe Coding and Agentic Engineering. The Line Is Verification. | daily.dev
og:description: A referenced Google whitepaper (attributed to Osmani, Saboo, and Kartakis) argues that vibe coding and agentic engineering aren't fundamentally different tools...
og:url: https://daily.dev/posts/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification--14yfikzdn
og:image: https://api.daily.dev/og/posts/14yFIkzdN.png
og:image:alt: Google Drew a Line Between Vibe Coding and Agentic Engineering. The Line Is Verification.
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Drew a Line Between Vibe Coding and Agentic Engineering. The Line Is Verification.

**[Noor Mohammad](https://daily.dev/sources/ew9hy5zthevyyefagop4g)** · [@noormohammad](https://daily.dev/noormohammad) · 1 min read · 0 upvotes · 1 comments

## Summary

A referenced Google whitepaper (attributed to Osmani, Saboo, and Kartakis) argues that vibe coding and agentic engineering aren't fundamentally different tools but represent different levels of structure, verification, and human judgment applied to the same AI-generated output. The core framing is 'Agent = Model + Harness,' with the claim that teams often procure a model, improvise a harness around it, then blame the model when things go wrong. A suggested practical exercise is proposed: take one feature and build it with specs, tests, evals, and a functioning kill switch.

## Content

Google's May 2026 Agents whitepaper (_The New SDLC With Vibe Coding_, by Osmani, Saboo, Kartakis) is long. The useful claim is short:

**Vibe coding and agentic engineering aren't different tools — they're different amounts of structure, verification and human judgment wrapped around the same AI output.** Same agent, same model, different factory.

Which kills the usual argument. It's not "is vibe coding bad," it's _where you sit on the spectrum for this task, and what enforces that position._

The vocabulary worth stealing: **Agent = Model + Harness.** Most teams procure the model and improvise the harness, then blame the model.

Includes a Monday move: one feature with specs, tests, evals and a real kill switch. 🔗
[https://medium.com/@thebuildersplaybook/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification-a8ce6828b195?sharedUserId=thebuildersplaybook](https://medium.com/@thebuildersplaybook/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification-a8ce6828b195?sharedUserId=thebuildersplaybook)

#ai #agents #softwareengineering #productivity #google #testing

## Community discussion

Top comments from developers on daily.dev.

**@noormohammad** · 0 upvotes

> The `200 or 429` example is why "verification" is the right axis rather than "quality" — the suite was green, the code looked done, and nothing in the pipeline was asserting the actual contract.
>
> Genuine question: what's in your harness beyond a test suite? Specs the agent is held to, held-out evals, tool permissions, a kill switch? My sense is most setups have exactly one of those and call it agentic engineering.

## Similar posts on daily.dev

- [From vibes to engineering: How AI agents outgrew their own terminology](https://daily.dev/posts/from-vibes-to-engineering-how-ai-agents-outgrew-their-own-terminology-qto3a4fys) · The New Stack · 0 upvotes · 0 comments
- [Vibe Coding vs Agentic Engineering](https://daily.dev/posts/vibe-coding-vs-agentic-engineering-3iei9hrlm) · Josh Hornby · 8 upvotes · 1 comments
- [The Death of the "Vibe Coding": Why Agentic Engineering is the New Standard](https://daily.dev/posts/the-death-of-the-vibe-coding-why-agentic-engineering-is-the-new-standard-ldvqvongw) · C\# Corner · 1 upvotes · 0 comments
- [The Vibing Continuum: How Software Will Vibe its Way Through Agentic Engineering](https://daily.dev/posts/the-vibing-continuum-how-software-will-vibe-its-way-through-agentic-engineering-kt8blquyf) · DevOps.com · 1 upvotes · 0 comments
- [Agentic Engineering](https://daily.dev/posts/agentic-engineering-vu5lypi1u) · Addy Osmani · 382 upvotes · 12 comments

---

Tags: [#google](https://daily.dev/tags/google), [#ai-agents](https://daily.dev/tags/ai-agents), [#ai-coding](https://daily.dev/tags/ai-coding), [#vibe-coding](https://daily.dev/tags/vibe-coding)

[View this post on daily.dev](https://daily.dev/posts/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification--14yfikzdn)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification--14yfikzdn","headline":"Google Drew a Line Between Vibe Coding and Agentic Engineering. The Line Is Verification.","text":"A referenced Google whitepaper (attributed to Osmani, Saboo, and Kartakis) argues that vibe coding and agentic engineering aren't fundamentally different tools but represent different levels of structure, verification, and human judgment applied to the same AI-generated output. The core framing is 'Agent = Model + Harness,' with the claim that teams often procure a model, improvise a harness around it, then blame the model when things go wrong. A suggested practical exercise is proposed: take one feature and build it with specs, tests, evals, and a functioning kill switch.","url":"https://daily.dev/posts/google-drew-a-line-between-vibe-coding-and-agentic-engineering-the-line-is-verification--14yfikzdn","datePublished":"2026-09-08T07:04:41.562Z","dateModified":"2026-09-13T20:47:50.325Z","author":{"@type":"Person","name":"Noor Mohammad","url":"https://daily.dev/noormohammad","image":"https://media.daily.dev/image/upload/s--3w4n0n-6--/f_auto/v1754054115/avatars/avatar_eW9hy5zTHEVyYeFaGOP4G?_a=BAMClqZW0","description":"Software Engineer | React, Next.js \u0026 scalable web apps | Writing on AI, blockchain \u0026 emerging tech","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":190}},"interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"comment":[{"@type":"Comment","text":"The 200 or 429 example is why “verification” is the right axis rather than “quality” — the suite was green, the code looked done, and nothing in the pipeline was asserting the actual contract.\nGenuine question: what’s in your harness beyond a test suite? Specs the agent is held to, held-out evals, tool permissions, a kill switch? My sense is most setups have exactly one of those and call it agentic engineering.","datePublished":"2026-09-08T07:05:39.166Z","url":"https://daily.dev/posts/14yFIkzdN#c-3ZcZDyBbc","author":{"@type":"Person","name":"Noor Mohammad","url":"https://daily.dev/noormohammad","image":"https://media.daily.dev/image/upload/s--3w4n0n-6--/f_auto/v1754054115/avatars/avatar_eW9hy5zTHEVyYeFaGOP4G?_a=BAMClqZW0"}}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/ew9hy5zthevyyefagop4g","name":"Noor Mohammad"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Noor Mohammad","item":"https://daily.dev/sources/ew9hy5zthevyyefagop4g"},{"@type":"ListItem","position":3,"name":"Google Drew a Line Between Vibe Coding and Agentic Engineering. The Line Is Verification."}]}
```

