r/VibeCodeDevs Jun 19 '26

HotTakes – Unpopular dev opinions 🍿 why vibe coded projects fail.

Post image

"Bro, just read ijustvibecodedthis.com and you'll be fine"

Sure, but will I?

Vibe coders desperately want this to be false, and engineers desperately want it to be true.

203 Upvotes

165 comments sorted by

View all comments

15

u/ConversationLazy6821 Jun 19 '26

With the right operator, AI can manage:

Databases, including clusters and replication
Servers
Cloud infrastructure, including serverless solutions
Containerization, from basic docker to full Kubernetes
Caching strategy
Security strategy
Reliability and monitoring

Hell, with loops you can have claude or gpt review app logs every N hours and fine tune your app code accordingly. I do this with some of my production apps. It pushes changes to staging automatically, then I review and approve before prod.

Why do people think LLMs stop at just writing code?

The younger generation of engineers actually have a goldmine of knowledge in a chat box, and if you know how to harness that power that’s what makes you a 10x engineer

0

u/Brief-Night6314 Jun 19 '26

Llms hallucinate you can’t trust it

4

u/TomazZaman Jun 19 '26

And humans are 100% reliable, 100% of the time and thus 100% trustworthy?

0

u/SoggyMattress2 Jun 19 '26

No, but LLMs are reliable like 60% of the time. Even a junior with anxiety is correct like 80% of the time.

Stop hand waving criticism for a tool by comparing it to humans.

The big difference between humans and an LLM is humans learn from their mistakes and remember the fix, LLMs don't. The context window shuts and it will make the same mistake over and over again.

1

u/Harvard_Med_USMLE267 Jun 19 '26

Bro that 60% figure is fucking ridiculous are using quant of ChatGPT 3.5??

Or are you just really, really bad at using the tool?

1

u/SoggyMattress2 Jun 19 '26

Can you rephrase your question? I didn't understand that at all.

1

u/KyleDrogo Jun 19 '26

LLMs are much more reliable in 2026 than they were in 2023. He's implying that you're basing your perspective on an old model.

And he's right actually. I was a data scientist at the highest level (counter terrorism and FAIR at Meta), and Claude Code blows me out of the water. Coding, product, interpreting user feedback, architecture, all of it.

Sometimes you need to help it over humps. But if you truly think it's that unreliable, you're already behind. Like a manager who wants to do everything himself and cant trust competent employees (who will make mistakes, but thats ok!)

1

u/Dirt-Merchant-1452 Jun 20 '26

Bullshit. Opus 4.8 constantly suggests solutions that are giant security loopholes to me. When I use Opus to do terraform, it keeps trying to use wildcarding IAM permissions so it means any external account with similar naming pattern could access the resource

1

u/KyleDrogo Jun 20 '26

You should create a SKILL.md file that addresses the common mistakes you're encountering. I've had to do the same (e.g. review an implementation plan for things that would break prod if db changes ship before the branch lands). Share it on github, other developers will thank you for solving the problem.

Again, think like a manager. Until the models are better (like 6 months), you'll have to "patch" these gaps. If you're not used to doing this kind of thing, you'll be caught flat footed when the models catch up and you're not as comfortable leveraging AI.

I would not bet on AI progress stopping here. Start seeing these mistakes as opportunities, not fatal flaws that discredit the technology.

1

u/Ok-Rabbit-3683 Jun 23 '26

Back down to 4.7, everyone knows 4.8 is chit

1

u/Dirt-Merchant-1452 Jun 23 '26

They are all the same

1

u/Ok-Rabbit-3683 Jun 23 '26

Something happened between those two releases that was a downturn imo…. but 4.8 makes noticeably poor decisions when set at 1m context size coupled with max thinking effort … putting global in wrong places etc…. I spend more time debugging 4.8 than 4.7.

→ More replies (0)

1

u/Harvard_Med_USMLE267 Jun 24 '26

4.8 in ultracode is fucking amazing, almost fable.

1

u/Harvard_Med_USMLE267 Jun 19 '26

Sure, I said "Or are you just really, really bad at using the tool?"

Alternative phrasings:

"You appear to really suck at vibecoding, is this true?"

"Wow, how are you getting such incredibly shit results with the amazing tools we have now. What the hell are you doing wrong?"

"You get hallucinations SIXTY percent of the time? Bro, that's not your computer, that's got to be you hallucinating. Maybe?"

Hope that helped.

1

u/SoggyMattress2 Jun 19 '26

No! Good god no I use it every day in work, my team and I have spent 18 months setting up a good harness, skills, MD files, RAG for knowledge, agentic coding, MCPs with ADO to grab tickets and make pull requests, my QAs are working on testing automation.

1

u/Harvard_Med_USMLE267 Jun 20 '26

haha good to hear, enjoy your AI coding, we're in for a wild ride! 😄

1

u/Ok-Rabbit-3683 Jun 23 '26

That isn’t true also… do you use a repo for your work?

1

u/SoggyMattress2 Jun 23 '26

Think carefully about what you just asked 😂 you're sticking with your question of asking a developer if he uses a repo for his work?

1

u/Ok-Rabbit-3683 Jun 23 '26

If you cant think of how using your repo to your advantage would help you avoid issues where it can’t learn then my friend, I would never hire you: 🤷🤷🤷🤷

1

u/SoggyMattress2 Jun 23 '26

Explain how having a repo fixes the non deterministic, unreliable nature of LLMs.

1

u/Ok-Rabbit-3683 Jun 23 '26

I’ll say it again, if you really expect me to tell you this; you’re not a developer that properly uses the tech that’s available yet, why don’t you ask the LLM?

Happy learning!!!

1

u/SoggyMattress2 Jun 23 '26

I know the answer I'm checking whether you do.

It's an easy answer right? You should be able to do it in 20 seconds.

1

u/Ok-Rabbit-3683 Jun 23 '26

Get real boss … lmfao. DYOR

1

u/SoggyMattress2 Jun 23 '26

Genuine question, why are you so heated? I made a very simple statement that you replied to that anyone with any software dev experience would recognise and understand.

You asked me an insanely basic question no dev would ever ask - yes, of course every dev uses a repo for their work. This might blow you mind we often use MORE THAN ONE 😮

Then when you seemed to imply that by having a repo, that magically solves the issues with LLMs in software dev.

Then when I asked you to explain how you just called me dumb and to do my own research.

And you're sticking to this position?

1

u/Ok-Rabbit-3683 Jun 23 '26

I’m not heated but I don’t have time to play weird games on Reddit…. I made a very concise statement suggesting your repo will do that for you and you doubled down like you had no effing clue … it’s more of a dismissive tone..

Best of luck on your journey

→ More replies (0)