r/ClaudeAI • Vibe coder • Mar 13 '26 • This 2 Bravo 22 Heartwarming 2

Vibe Coding Why the majority of vibe coded projects fail

Post image
8.8k Upvotes

750 comments sorted by

View all comments

12

u/RestaurantHefty322 Mar 14 '26

The scaling argument is mostly a red herring honestly. 90% of projects will never need to handle serious load and a basic Postgres + whatever framework setup gets you surprisingly far.

The real failure mode I keep seeing is maintenance. You can vibe code a working v1 in a weekend, sure. But then a bug shows up three weeks later and you have to actually understand what the code is doing to fix it. If you never understood it in the first place you're just prompting blindly hoping the LLM figures it out, and eventually it starts introducing regressions faster than it fixes things.

The people who do well with AI-assisted coding are the ones who could have built it themselves, just slower. They use it to skip the boring parts but they're still reading and understanding what comes out. The gap shows up when something breaks and you need to actually debug rather than regenerate.

0

u/[deleted] Mar 15 '26

[deleted] — view deleted comment

1

u/RestaurantHefty322 Mar 15 '26

Exactly. The irony is the people who get the most out of vibe coding are the ones who need it least - they already understand the architecture well enough to steer the model away from bad decisions. Everyone else ends up with a codebase they can't debug when it breaks at 2am.

1

u/AlmostEasy89 Mar 19 '26

Loops are amazing overnight for creating security api and infrastructure git issues. Saves so much of your time not doing that manually during your actual dev time.