--- title: Agentic Engineering | daily.dev description: Agentic engineering is a disciplined approach to AI-assisted software development that distinguishes itself from "vibe coding" through human oversight and... canonical: https://daily.dev/posts/agentic-engineering-vu5lypi1u twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Agentic Engineering | daily.dev og:description: Agentic engineering is a disciplined approach to AI-assisted software development that distinguishes itself from "vibe coding" through human oversight and... og:url: https://daily.dev/posts/agentic-engineering-vu5lypi1u og:image: https://api.daily.dev/og/posts/vu5lYpI1U.png og:image:alt: Agentic Engineering 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. # Agentic Engineering **[Addy Osmani](https://daily.dev/sources/addy)** · [@addyosmani](https://daily.dev/addyosmani) · 7 min read · 381 upvotes · 12 comments ## Summary Agentic engineering is a disciplined approach to AI-assisted software development that distinguishes itself from "vibe coding" through human oversight and engineering rigor. While vibe coding means accepting AI output without review (useful for prototypes and MVPs), agentic engineering involves treating AI agents as tools that handle implementation under careful human direction. The workflow requires writing specs before prompting, reviewing every diff, running comprehensive test suites, and maintaining ownership of the codebase. This approach disproportionately benefits senior engineers with strong fundamentals, as it trades typing time for review time and demands architectural thinking over raw code generation. The rise of AI coding raises rather than lowers the bar for software engineering craft. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@abhishekdeb** · 37 upvotes > Nice distinction between vibe coding and agentic engineering. > > My daily development setup: > > 1. Define ‘[instructions.md](http://instructions.md)’ with coding style, project structure, things not to do (e.g do not use any, stricter typechecks), project flow, major components/services. This is one time setup but reduces lot if cognitive load and ‘trial and error’ prompts. > 2. For the new feature, ask gpt to create spec file. > 3. Manually review and edit the spec with clear input, output, some edge cases, the actual process broken down into multiple tasks. All of these with a status field. > 4. Ask... **@a\_meb\_a** · 10 upvotes > better than vibe coding **@telli** · 9 upvotes > I miss the good old days where Computer Science was not fractured in empty buzzwords. **@abaracedo** · 3 upvotes > Addy always brings gems with his writtings **@georgeongoro** · 0 upvotes > This is a timely breakdown of where software engineering is actually heading. If Vibe Coding was the experimental, 0-to-1 phase of AI-assisted development, Agentic Engineering is the operational framework that makes it production-ready. > > ​The shift from being a "Code Writer" to a "System Orchestrer" is the most significant takeaway here. We are moving away from single-prompt hope-and-pray cycles toward structured, multi-agent workflows where: > > - ​Design is the Bottleneck, Not Syntax: Your ability to define clear interfaces and system boundaries becomes your greatest leverage. > - ​Verification... ## Similar posts on daily.dev - [Agentic Engineering: A Practitioner's Playbook](https://daily.dev/posts/agentic-engineering-a-practitioner-s-playbook-9nmcufzid) · Domino Data Lab · 0 upvotes · 0 comments --- Tags: [#ai](https://daily.dev/tags/ai), [#testing](https://daily.dev/tags/testing), [#architecture](https://daily.dev/tags/architecture), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/agentic-engineering-vu5lypi1u) ```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":"TechArticle","headline":"Agentic Engineering","url":"https://daily.dev/posts/agentic-engineering-vu5lypi1u","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/agentic-engineering-vu5lypi1u"},"datePublished":"2026-02-05T03:40:22.396Z","dateModified":"2026-02-06T00:00:21.988Z","description":"Agentic engineering is a disciplined approach to AI-assisted software development that distinguishes itself from \"vibe coding\" through human oversight and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0cb2750533ee4866691cdc36b090a0a4?_a=AQAEulh","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0cb2750533ee4866691cdc36b090a0a4?_a=AQAEulh","isAccessibleForFree":true,"articleSection":"Addy Osmani","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Person","name":"Addy Osmani","url":"https://daily.dev/addyosmani","image":"https://avatars2.githubusercontent.com/u/110953?v=4","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":5320}},"commentCount":12,"discussionUrl":"https://daily.dev/posts/agentic-engineering-vu5lypi1u","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":381},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":12}],"keywords":"ai,testing,architecture,code-review","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Addy Osmani","item":"https://daily.dev/sources/addy"},{"@type":"ListItem","position":3,"name":"Agentic Engineering"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/agentic-engineering-vu5lypi1u","comment":[{"@type":"Comment","text":"Nice distinction between vibe coding and agentic engineering.\nMy daily development setup:\n\nDefine ‘instructions.md’ with coding style, project structure, things not to do (e.g do not use any, stricter typechecks), project flow, major components/services. This is one time setup but reduces lot if cognitive load and ‘trial and error’ prompts.\nFor the new feature, ask gpt to create spec file.\nManually review and edit the spec with clear input, output, some edge cases, the actual process broken down into multiple tasks. All of these with a status field.\nAsk clause to create sanity and basic tests cases against the spec. Acts as guardrails.\nAsk claude to pick the 1st task from spec based on status, start working on it.\nSpawn new agent to run qa (peer review) on the generated code. Based on feedback, ask 1st agent to fix them and keep close eye on the spec and tests.\nOnce QA and local tests say all good, I manually test it against spec and end goal.\nAfter this, i manually review all the changeset\nIf something is missed, i update it in spec file and ask claude to re-reciew it and fix it.\nFinally run another claude agent to do critical code review from senior engineer perspective to check for severities, owasp issues, backdoor loopholes.\n\nI know this is a lot but, i am way more confident with this approach where I still feel accountable for owning the codebase.\nTurns out, i was doing agentic engineering and downselling it as vibe coding.","datePublished":"2026-02-11T03:03:57.466Z","dateModified":"2026-02-11T03:07:55.780Z","url":"https://daily.dev/posts/vu5lYpI1U#c-n1ctq3K9G","author":{"@type":"Person","name":"Abhishek Deb","url":"https://daily.dev/abhishekdeb","image":"https://lh3.googleusercontent.com/a/ACg8ocJ07shqjSJq3IQQxHqwgJv9r3DoA6lY9jVIF4C5J-W1z2xrj0B2FQ=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":37}},{"@type":"Comment","text":"better than vibe coding","datePublished":"2026-02-09T11:09:27.655Z","url":"https://daily.dev/posts/vu5lYpI1U#c-OysrHtP2v","author":{"@type":"Person","name":"Phillippe Michel Weir","url":"https://daily.dev/a_meb_a","image":"https://media.daily.dev/image/upload/s--BwH-uTMq--/f_auto/v1740136991/avatars/avatar_N403VFK9lAHNRwlSAhl1h"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":10}},{"@type":"Comment","text":"I miss the good old days where Computer Science was not fractured in empty buzzwords.","datePublished":"2026-02-13T09:02:50.151Z","url":"https://daily.dev/posts/vu5lYpI1U#c-9mwjgVceK","author":{"@type":"Person","name":"Gökhan Yesilyayla","url":"https://daily.dev/telli","image":"https://media.daily.dev/image/upload/s--uvOVZKth--/f_auto/v1747040086/avatars/avatar_8OZxUEpFYzWHRGdCLpAZa?_a=BAMClqUq0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":9}},{"@type":"Comment","text":"Addy always brings gems with his writtings","datePublished":"2026-02-12T08:03:53.942Z","url":"https://daily.dev/posts/vu5lYpI1U#c-QxP9NkwAB","author":{"@type":"Person","name":"Alejandro Bar Acedo","url":"https://daily.dev/abaracedo","image":"https://avatars.githubusercontent.com/u/9487675?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"This is a timely breakdown of where software engineering is actually heading. If Vibe Coding was the experimental, 0-to-1 phase of AI-assisted development, Agentic Engineering is the operational framework that makes it production-ready.\n​The shift from being a “Code Writer” to a “System Orchestrer” is the most significant takeaway here. We are moving away from single-prompt hope-and-pray cycles toward structured, multi-agent workflows where:\n\n​Design is the Bottleneck, Not Syntax: Your ability to define clear interfaces and system boundaries becomes your greatest leverage.\n​Verification is Automated: We aren’t just generating code; we’re generating the agents that test and audit that code.\n​Context is King: The vibe is replaced by RAG-enhanced agents that understand your specific codebase, style guides, and business logic.\n\n​Thanks Addy for sharing the read.","datePublished":"2026-02-13T20:06:01.466Z","url":"https://daily.dev/posts/vu5lYpI1U#c-uCRuxXJOJ","author":{"@type":"Person","name":"George Ongoro","url":"https://daily.dev/georgeongoro","image":"https://media.daily.dev/image/upload/s--jXl_MleY--/f_auto/v1779359556/avatars/avatar_JCfNZtLPNzTFifdLCBjRk?_a=BAMAMiWQ0"}}]} ```