---
title: "\"Vibe Coding\" vs Reality"
url: https://daily.dev/posts/vibe-coding-vs-reality-lkduufhfk
source_url: https://cendyne.dev/posts/2025-03-19-vibe-coding-vs-reality.html
type: article
source: "Lobsters"
published: 2025-03-21T08:47:49.725Z
updated: 2025-03-21T08:48:18.815Z
tags: ["ai", "devtools", "github", "llm"]
reading_time: 11
upvotes: 106
comments: 16
language: 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" vs Reality

**[Lobsters](https://daily.dev/sources/lobsters)** · 11 min read · 106 upvotes · 16 comments

## Summary

Vibe coding refers to a trend where developers use large language models (LLMs) to produce software from simple descriptions in natural language, without focusing on detailed coding practices. While these tools have made software development more accessible, they suffer from limitations like repeating mistakes, making inappropriate assumptions, and lacking long-term memory. Current models can assist in creating mockups but are not reliable enough for producing secure, production-quality software without human intervention and expertise.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://cendyne.dev/posts/2025-03-19-vibe-coding-vs-reality.html>

## Community discussion

Top comments from developers on daily.dev.

**@cristiansarmiento** · 23 upvotes

> Vibe coding refers to a trened where NON DEVELOPERS are trying to be one.

**@kieranoleary** · 8 upvotes

> If you are a developer and can't incorporate vibe coding into your workflow than prompting is likely your issue.  AI models ARE capable of producing good code but you need to be very specific.  If you  just say 'go do this however you want' it will give you spaghetti code.  Use your voice and speak in detail and create planning files and you will be surprised how useable it is. I built vibebreath.com this way

**@skeptiq** · 7 upvotes

> Vibe coding in my case: AI vomits lots of code, I lose more time to rectify it. Eventually I continue to discover bugs over bugs.
>
> My take: AI can produce code but cannot solve the problem.

**@rusznic** · 6 upvotes

> Vibe coding helps you write a lot of code with little understanding at first, but the final refinement - often half the work - requires real skill. Relying on AI makes this stage harder because shallow understanding comes at a cost

**@terryhunt** · 1 upvotes

> This vibe coding is like hiring Fiverr to do the work we must fix. We use ChatGPT and Claude for coding, but we don't always copy/paste the code right away without reading it or understanding the function/logic of the code. These AIs are great for documenting and finding little things, but not for complicated things.

## Similar posts on daily.dev

- [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments
- [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments
- [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments
- [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments
- [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments

---

Tags: [#ai](https://daily.dev/tags/ai), [#devtools](https://daily.dev/tags/devtools), [#github](https://daily.dev/tags/github), [#llm](https://daily.dev/tags/llm)

[View this post on daily.dev](https://daily.dev/posts/vibe-coding-vs-reality-lkduufhfk)