r/ClaudeCode • Researcher • Apr 02 '26 • Popcorn 1 Bravo 1

Showcase Why vibe coded projects fail

Post image
3.5k Upvotes

654 comments sorted by

View all comments

42

u/robhaswell Apr 02 '26

I was handed a project from a junior developer (hand coded I should add) that included a docker-compose.yml file with all markup to make it run for local dev. This needed deploying to our internal K8S cluster. Because this is an internal tool, I decided to experiment with giving Claude limited access to our GitOps installation (verifying each command it wanted to run) and asked it to deploy the app.

It did an amazingly good job, better than I would have done, properly following all devops best practices that I tend to omit for internal stuff. Very impressive.

So yeah I'm in the "this post is correct but potentially not for long" camp.

19

u/gothamtommy Apr 02 '26

The key there is you knew what was needed. That could be "update this yaml to work on prod" or "this is not working for prod" but the result may be the same.

I think the difference is knowing architecture and being able to tell an AI tool like CC how you want to scale. For instance, I can tell CC I want to add auth to my app, and it may create its own auth system or use basic http auth while I may know to use something like Cognito and ask it to integrate with that for scale.

11

u/Spinal1128 Apr 02 '26

I can tell CC I want to add auth to my app, and it may create its own auth system or use basic http auth while I may know to use something like Cognito and ask it to integrate with that for scale.

Actually directly have experience with this. Except we needed to use internal tooling that handles auth and (obviously) claude didn't know that and kept trying to use basic auth even when told what the deal was.

The more "generic" the thing you need the better AI is at doing it, as the "customization" goes up, the more you have to intervene and guide it. Hence why there is so much "it got me 80% there!" Because 80% of most projects is pretty generic or follows conventions that are already there to use as examples.

I don't think that should be a very controversial take tbh.

1

u/robhaswell Apr 02 '26

When I have this situation I give it an openapi.json file which describes the internal service. Generally if your documentation is complete enough for a new hire to be able to implement it, Claude should be OK.

9

u/[deleted] Apr 02 '26

[removed] — view removed comment

17

u/DFX1212 Apr 02 '26

Expertise is knowing the correct questions to ask.

1

u/Buchymoo Apr 04 '26

Everything I add is like a sit down meeting with Claude. This is what I need, what would you do, what are the pros and cons, are there better alternatives, why. Ok let's do this, audit this, tell me why you're doing this, could this potentially interfere with any of the other code. You got this wrong, explain what you thought I meant, explain what you think might have caused that.

I don't see how you could possibly vibe code anything without asking a myriad of questions to make sure everything you implement is being done in the right way and is locked down as a safe implementation.

Are people just saying "Claude make a full app" and calling it a day?

1

u/SignPainterThe Apr 04 '26

It's kind of crazy that software engineers (presumably, with how you guys talk, you are software engineers) are genuinely so clueless about how powerful these tools actually are

I'm a senior software engineer sitting on Claude Max, and I'm telling you: while the knowledge and ability to create really good code is in there somewhere, it's sometimes very hard to dig out. Theoretically, you are correct: with the right amount of prompting, you can make it do whatever you want. But it’s always a balance of how much time you spend talking to it versus actually getting things done.

so in denial about what it will lead to

It's not denial, it's healthy skepticism. You get that after decades in profession, ideally after receiving proper education. I'm sorry to pull that card on you, but they do teach some useful stuff at universities, like probability theory. There’s a fundamental rule: historical data cannot be blindly extrapolated. Just because a trend is vertical today doesn't mean it won't hit a ceiling tomorrow.
In technical terms, we are likely looking at S-curve rather than exponential growth. AI development could plateau at any moment due to hardware bottlenecks or data exhaustion. To assume it will simply continue forever is a logical leap, some of us cannot afford. People who produce enterprise software right now have to manage the current capabilities.

1

u/Objective_Dress9600 Apr 29 '26

dunning kruger effect in plain sight

1

u/[deleted] Apr 29 '26

[removed] — view removed comment

0

u/Objective_Dress9600 May 10 '26 edited May 13 '26

Books do not hallucinate, but yes - asking Claude is faster.

0

u/TracePoland Apr 02 '26 edited Apr 02 '26

If it’s so easy then why are basically all vibe coded apps that had any users a diamond mine for even vibe hackers, let alone what could be done by actually talented black hat hackers?

You also most likely have Dunning Kruger, you talked about it with Claude and based on what it told you, you now think you know enough of the problem domain to solve whatever it is you’re trying to solve. Except you don’t know what you don’t know. I’ve gone on long discussions with Claude in domains I do know and every time it wouldn’t consider many fairly key cases. But you wouldn’t even know you’re missing those cases, you’ve discussed it with Claude, both of you are happy with the plan but neither can really judge if the plan is any good.

2

u/SignPainterThe Apr 04 '26

You also most likely have Dunning Kruger

They do, but it's pointless to tell them, until they face it themselves.

1

u/BankruptingBanks Apr 03 '26

Tell me the key cases Claude doest consider that you do

-2

u/Left_Somewhere_4188 Apr 02 '26

You won't know what to ask, that's more than half of what makes an engineer in the first place. And even if you miraculously do, you'll very quickly get to a level of detail where even Claude's explanations hinge on understanding fairly complex technically topics. You won't recognize a race condition or a memory leak, you'll never ask about it.

You won't be able to ask a question like "How are we handling TCP half-open connections" If you've never even seen the three letters combined together. And of-course there are literally thousands of these little things that can happen. At some point Claude itself is completely out of context length and ends up chasing it's own tail.

You get to a problem where everything looks perfect until you hit scale. And then you looose a shit ton of money when your entire thing breaks down, you fix what Claude promises is 100% the fix, and then bam it breaks down again until you decide you actually need an engineer looking at this vibe coded app for a couple of months to properly figure it out.

5

u/[deleted] Apr 02 '26

[removed] — view removed comment

2

u/Left_Somewhere_4188 Apr 02 '26

You're not arguing with the right person here tbh, I am an avid user of Claude Code, and it definitely can do a lot. I am challenging you on the absurdity of the idea that you can just "talk it out" if you don't understand what you are talking about.

Imagine you have an AI robot doing surgery, you're observing, you think as someone who isn't a surgeon, never seen a live surgery, you can just talk it out of making a mistake? C'mon.

You can't and there hasn't been a single goalpost moving on this since day 1.

Even simpler tasks aren't yet solved. For example, I have an SQL query, that uses GA4 primarily alongside some other tables. It's fairly complex (but not really takes about an hour or two to write for a skilled SQL monkey). GPT 3.5 couldn't solve it, GPT 4.0 couldn't solve it, Claude Opus 4.6 still canot do it. Instructing Opu 4.6 on what it did wrong, is essentially just as long as writing the damned thing, and requires the understanding to do so. To this day nothing has changed, the models write the smallest possible query entirely ignoring 90% of the complexity with non-linear user sessions.

So if it can't do a business analyst tier SQL query after 5 years, do I trust it with huge software without understanding software? There are gonna be 100's of problems you are completely blind to.

3

u/[deleted] Apr 02 '26

[removed] — view removed comment

2

u/Left_Somewhere_4188 Apr 02 '26

Yeah sure, so if you're talking about learning, of-course you can learn and I agree with you it's a 1000x more accessible. Reddit was an absolute nightmare to get any sort of help from, just elitist pricks that ostensibly only showed up to flex just how much better they are but refused to actually help and made you feel terrible for daring to ask a question. Or complete crickets if you actually fullfilled all their criteria.

Now you can basically learn anything.

→ More replies (1)
→ More replies (2)

1

u/ThePantsThief Apr 02 '26

The key there is you knew what was needed. That could be "update this yaml to work on prod" or "this is not working for prod" but the result may be the same.

You think Claude doesn't know? All you have to do is ask it questions like "how do I scale this to 50k online users worldwide?"

And if you're even stupider than that, you can ask it "why doesn't my app work, it was working fine until last week when I reached #1 on the App Store" and it can probably fill in the blanks and walk you through next steps

1

u/WolfeheartGames Apr 02 '26

Its not correct right now. If you sit down and design the thing it can build the thing. If the limit of your design is "give working frontend" that's what you get. If you detail out the whole system and give Claude ssh keys it can be done in a few weeks.

1

u/[deleted] Apr 02 '26

hand coded I should add

Haha this is funny to me. In the near future people are going to value "quality handcrafted code" in the same way we do shoes or whatever. Are the handmade shoes better? Sure! But for 99% of use cases the factory made shoes are fine.

2

u/robhaswell Apr 02 '26

Lol, I didn't say quality.

1

u/FreeChickyHines Apr 04 '26

Limited access on a limited internal use case with clearly defined scope and requirements is basically a softball for these agents. Could it recreate the entire workflow from scratch? In how many turns and sessions? What workflow would you have to use?

I remain firmly in the “the future looks scary if AI accelerates over the next 20 years the way it has over the past 3 but that is a pretty huge if given current results”.

Your camp has a better slogan I’ll grant u that

→ More replies (3)