<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x" -->

---
title: Vibe Coding Isn't the Problem. Calling It Engineering Is
description: An engineer with ten years of experience argues that vibe coding — writing prompts and shipping AI-generated code without editing or reviewing it — is...
canonical: https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Vibe Coding Isn't the Problem. Calling It Engineering Is | daily.dev
og:description: An engineer with ten years of experience argues that vibe coding — writing prompts and shipping AI-generated code without editing or reviewing it — is...
og:url: https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x
og:image: https://api.daily.dev/og/posts/0Sh173S4X.png
og:image:alt: Vibe Coding Isn't the Problem. Calling It Engineering Is
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.

# Vibe Coding Isn't the Problem. Calling It Engineering Is

**[DEV](https://daily.dev/sources/devto)** · 4 min read · 1 upvotes · 0 comments

## Summary

An engineer with ten years of experience argues that vibe coding — writing prompts and shipping AI-generated code without editing or reviewing it — is fundamentally different from engineering, which requires reviewing, understanding, and taking ownership of code. The piece distinguishes three modes: vibe coding (no review), AI-assisting (AI writes, human reviews everything), and AI-assisted (human and AI collaborate with human driving). The author argues vibe coding is fine for personal projects but reckless for systems handling money or sensitive data, and that skipping the two-to-four weeks needed to learn coding basics before shipping production systems is irresponsible. Comments largely agree, with some pushing back on the narrow definition of vibe coding and others adding that code review alone doesn't cover operational risks like misconfigured servers or backups.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://dev.to/georgekobaidze/vibe-coding-isnt-the-problem-calling-it-engineering-is-lm1>

## Questions this post answers

### What is the difference between vibe coding and AI-assisted coding?

Vibe coding means writing a prompt and shipping the AI's output without editing or reviewing any of it, so the person may not understand the code at all. AI-assisted or AI-assisting workflows require the human to review everything the AI generates or to actively drive the coding alongside the AI, catching edge cases and verifying correctness before shipping. The distinguishing factor is whether the code gets reviewed and understood, not who typed it.

_Anyone weighing how much to trust AI-generated code can compare takes on this distinction through daily.dev._

## Similar posts on daily.dev

- [Vibe Coding vs Agentic Engineering](https://daily.dev/posts/vibe-coding-vs-agentic-engineering-3iei9hrlm) · Josh Hornby · 8 upvotes · 1 comments
- [The Basics of Vibe Engineering](https://daily.dev/posts/the-basics-of-vibe-engineering-ljipaqa3r) · Towards Data Science · 13 upvotes · 1 comments

---

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

[View this post on daily.dev](https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x)

```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":"Vibe Coding Isn't the Problem. Calling It Engineering Is","url":"https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x"},"datePublished":"2026-09-14T01:17:29.462Z","dateModified":"2026-09-15T04:29:44.688Z","description":"An engineer with ten years of experience argues that vibe coding — writing prompts and shipping AI-generated code without editing or reviewing it — is...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0a123c4ccf86054a984cab8e32f73b10?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0a123c4ccf86054a984cab8e32f73b10?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DEV","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":"Organization","name":"DEV","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/devto","url":"https://daily.dev/sources/devto"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai,ai-coding,code-review,vibe-coding","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DEV","item":"https://daily.dev/sources/devto"},{"@type":"ListItem","position":3,"name":"Vibe Coding Isn't the Problem. Calling It Engineering Is"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/vibe-coding-isn-t-the-problem-calling-it-engineering-is-0sh173s4x#faq","mainEntity":[{"@type":"Question","name":"What is the difference between vibe coding and AI-assisted coding?","acceptedAnswer":{"@type":"Answer","text":"Vibe coding means writing a prompt and shipping the AI's output without editing or reviewing any of it, so the person may not understand the code at all. AI-assisted or AI-assisting workflows require the human to review everything the AI generates or to actively drive the coding alongside the AI, catching edge cases and verifying correctness before shipping. The distinguishing factor is whether the code gets reviewed and understood, not who typed it. Anyone weighing how much to trust AI-generated code can compare takes on this distinction through daily.dev."}}]}
```

