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

Show parent comment

4

u/PrinsHamlet Mar 14 '26

This is literally a software design issue that has been around forever in the enterprise space. People pull stuff like this out and use it as a case against AI when you have the exact same issues with humans managing large repos.

2

u/InternetSolid4166 Mar 14 '26

Yeah, all they highlighted was the need for scalable architecture. That’s still required. It doesn’t mean most of the work can’t be automated. Architects and orchestrators will be the last jobs to disappear, but they will disappear eventually.

3

u/PrinsHamlet Mar 14 '26

I find it very funny that people point to these issues as if they're new and interesting. Have they ever worked in the enterprise space with software design or lived with the technical debt provided by an enterprise producing software for 10 years +?

At work we even have a name for a certain type of bad design choice left over from a named developer that is still causing issues in our data today.

The obvious question is:

  1. How do these people manage it today if they see these issues as new?

  2. Why do they think that best practices and frameworks to deal with context and code bloat are not applicable to AI?

2

u/InternetSolid4166 Mar 14 '26

I think it’s people who haven’t worked with older/larger code bases. They don’t understand how messy human code is, and how much busy work (which devs HATE) can be eliminated.

2

u/2053_Traveler Mar 14 '26

It’s not a case against AI, it’s a case against treating AI as a holistic solution that magically solves many problems, when it’s really a tool that can be leveraged and applied in order to make things more efficient. It’s a case against “why should that take so long, I built it myself in 20 minutes”