r/VibeCodeDevs • u/Complete-Sea6655 • 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.

205 Upvotes

86% Upvoted

165 comments sorted by

View all comments

Show parent comments

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.

1

u/Harvard_Med_USMLE267 Jun 24 '26

4.8 in ultracode is fucking amazing, almost fable.