[lil-lugger]

As someone who vibes codes web apps that are being used by people, they take way way longer than initially expected. The prototype can take one shot, and the full prod implementation can take weeks to months. If you aren’t able to stick it out it will die but if you are willing to learn how to prompt to integrate Auth, email, security, performance than you can create truly incredible apps with no coding experience. But it’s basically a new skill in and of itself. Claude Code already gets the prototype to final product gap down a lot because it’s so good and getting better but it still makes mistakes and needs lots and lots and lots of nudging and directing and reminders and writing docs and getting other agents to check work based on docs ect.

[techblueberry]

When you say with no coding experience, what does that mean to you? I can get near miraculous results from vibe coding, but it often gets stuck in weird “bug loops” where it goes back and forth between broken states, and I have to understand either like bracket formatting, or be able to research library failures and conflicts. I suppose with no coding experience I could maybe muddle through, but itw would require hours of patience and probably learning some coding fundamentals to do something I can identify in sometimes seconds.

[lil-lugger]

Literally could only do basic html css before. Now I can build solid Sveltekit web apps from scratch. It’s still hard and frustrating. I’ve spent all day trying to get OTP auth working it’s very frustrating it misses things. But other times you can one shot whole features. Supabase MCP has been an absolute game changer. Database fluidity in development is really key. Trying to push migrations and generate types manually beforehand add so much time.

[tstrimple]

This has been my experience as well. I've gotten really good results from Claude Code, but sometimes I have to press esc when I see it doing something stupid and course correct. It really seems to struggle with recursive solutions to problems or deeply nested constructs. Because I have a programming background, I know better when to interrupt and provide different directions or know when to abandon contexts better than someone without "coding experience" ever could. Just the years and years of debugging experience on your own projects will position you infinitely better than someone who has never really had to dig into complex problems and figure out what's going wrong. Sometimes you have to tell the agent specifically which logs to look into or which likely problem spaces it's encountering and knowing what sort of logs exist on a system is important for that.

[locknitpicker]

> I can get near miraculous results from vibe coding, but it often gets stuck in weird “bug loops” where it goes back and forth between broken states, and I have to understand either like bracket formatting, or be able to research library failures and conflicts.

In my experience this is mainly caused by a lack of investment in tests.

Vibe-coding excels when paired with test-driven development, because TDD approaches serve as validators and problem constrains. Often coding agents get stuck on but loops because they have neither context nor feedback on what represents a broken state. Tests fix both problems, and if you stop to add one then your bug loops quickly vanish.

[zephyrthenoble]

So vibe coders need to know how to write tests? I doubt that lowers the effective barrier of entry to coding very much.

I assume you can't trust the LLM to write these tests, since you are writing tests so the LLM will stop it's bug loop...

[locknitpicker]

> So vibe coders need to know how to write tests?

Inasmuch as they need to know how to write code.