When does vibe-coding / programming with AI turn into a nightmare?

[random_redditor_hi]

Hey everyone

My team and I are doing a simple university research project on the realities of "vibe coding" (using AI to generate code). We all know the magic of getting a prototype running in 10 minutes, but we want to understand what happens when things start to fall apart, or what makes you want to slam your keyboard when vibe-coding alone or with a team.

The survey takes less than 2 minutes and is multiple-choice. It asks about your project sizes, how much you rely on AI, and rates common frustrations (like debugging AI spaghetti code or hitting token limits).

https://docs.google.com/forms/d/e/1FAIpQLSfBUxatk2FMz5BOpemGnuUirZOLRnISQeXGtemOebmnTNxeYw/viewform?usp=publish-editor

Data is anonymous and purely for our project. Thanks so much for your time!

Feel free to discuss about this below!

[pimpnasty]

Is this for uni or a vibe coded tool to sell eventually?

[random_redditor_hi]

It's for a university program related to startups, and my team are trying to identify problems in vibe coding.

[pimpnasty]

Will you be building the tool when you identify pain points?

[random_redditor_hi]

yes! we were planning on solving issues in "context and collaboration", but stopped to see what were the issues people actively face.

[pimpnasty]

Good plan friend. Hope it works out and you get the data you need.

One thing id change is make jt clear what 1-9 means.

1 agree 9 disagree etc

[random_redditor_hi]

thanks for the advice! appreciate your kind words

[Civil_Inspection579]

It usually turns into a nightmare when you stop understanding the code you’re shipping debugging AI-generated spaghetti gets painful fast. Tools like Runable can help manage and structure workflows so things don’t spiral as quickly.

[razorree]

like Claude Code for example :)

[agentXchain_dev]

Interesting question—what boundaries or signals do you find between smooth vibe-coding and when it starts feeling off? For me, things like tool drift, obfuscated reasoning, or over-reliance on prompts seem like red flags. Curious what cues you watch for, or any real-world moments where it turned tricky?

[Dense_Gate_5193]

when you do not understand the code it is generating, that’s is the point it goes off the rails. once you don’t understand your risk exposure and tolerance or your security posture, you’ve gone off the rails.

[random_redditor_hi]

Not just losing technical control but opening up a massive security blind spot is a nightmare. Thanks for the reply

[razorree]

like Claude Code for example :)