Hi, what kind of problem are you having? Vibe coding itself isn’t really the issue — the bigger challenge is coming up with an idea and figuring out how it can be monetized. AI is great for helping you build whatever you have in mind, as long as it doesn’t require true innovation. At least from my perspective, AI can’t really conceive and create something genuinely new — or at least not in the way we currently use it.

I watched your video and what you’re saying about code quality and refactoring absolutely makes sense. On the other hand, if vibe coding gives you a chance to build something you find interesting, it’s sometimes perfectly fine to move fast, get to an MVP, and see whether it actually makes sense.

Either way, it’s a cool topic for discussion.

That sounds fine, maybe you're still learning to prompt for what you want but ai-assistance with manual review seems like a sweet spot instead of vibe coding (or not reviewing output at all)

So, ask ai for help on prompting or look up ways to prompt more for what you want or continue to practice?

> I'm tired of trying to make vibe coding work for me

PATIENT: "Doctor, when I ram my head into the wall like this, it hurts."

DOCTOR: "Stop doing that."

Seriously, it's not written anywhere that you must use vibe coding. Feel free to do other things instead:

a. Code manually

b. Code manually using a coding assistant to suggest completions

c. Use spec-driven development with OpenSpec, SpecKit, BMAD-Method, etc.

d. Use visual programming / low-code / no-code etc.

e. Use old-skool deterministic code generators that generate code from UML or some other intermediate representation