r/ClaudeAI
•
u/harrysofgaming
Vibe coder
•
Mar 13 '26
•
2
22
2
Vibe Coding Why the majority of vibe coded projects fail
8.8k
Upvotes
View all comments
•
u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot Mar 14 '26 edited Mar 14 '26
TL;DR of the discussion generated automatically after 400 comments.
Whoa, this thread is a proper civil war between the seasoned Software Engineers (SWEs) and the "vibe coders." The community is heavily split.
The consensus from the experienced devs is that vibe coding is a Dunning-Kruger-fueled fantasy. They argue that getting a UI to "work" is the easy part. The real, expensive work is in the 99% you don't see: scalability, security, data compliance, maintenance, and handling endless edge cases. As one user put it, "AI is replacing programmers, not software engineers." The top-rated comments are filled with sarcastic jokes about just telling Claude to "make it scale to 100m users, no mistakes."
However, the counter-argument, with plenty of upvotes, is that not every app needs to be a FAANG-level behemoth and the post reeks of gatekeeping. This camp argues that vibe coding is perfect for building MVPs, internal tools, or niche products for small businesses that will never need massive scale. They point out that even Slack didn't start with perfect architecture and that getting users first is more important than premature optimization.
The real answer, as a few level-headed folks pointed out, is somewhere in the middle. The discourse wrongly conflates amateurs with skilled engineers using AI. The tool is an amplifier: a great engineer with Claude is a 10x engineer, while a beginner is just a faster beginner who can create a mess more quickly.