On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit

I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.

Not looking to stir up trouble here, but genuinely asking. The first version of my app was mostly put together with prompts, and it took about four hours to have a functional demo. Then came three weeks of fixing bugs that the prompt-based approach caused, like data type mismatches, weird behavior when form fields were empty, etc.

I suppose adding up total time spent, it may not have been quicker than if I had written the whole thing from scratch, though it certainly felt quick at the time because early success was very tangible.

Last summer, the idea for my SaaS, Xolora, started to take shape. Around the same time, the concept of vibe coding was blowing up. As a non-technical founder, it sounded like a dream come true. No coding experience? No problem, just let AI handle it.

The beginning was incredibly promising. Using Emergent made me feel unstoppable. I was seeing my idea come to life.

Hey everyone,

I've built my product around traditional SaaS pricing (monthly tiers), but I m starting to wonder if that model is getting outdated, especially with more AI-powered and compute-heavy tools entering the market.
That shift requires real architectural changes, instrumentation, metering, billing logic, and UI changes, not just pricing tweaks. It s something I m starting to seriously think about for my own product.

In particular, AI usage has real COGs (every prompt costs money), and I m seeing more platforms experimenting with usage-based models, or hybrids like SaaS base + usage + overage.

For those of you building AI or compute-intensive tools:

Doing a little side project in Cursor and I ve observed a pattern each time I ask it to implement a tiny feature close to my authentication code, it rewrites some parts of the authentication process that were untouched by me, in a manner that seemed more elegant but actually affected the functionality. Even removing a session expiration check at one point during some unrelated refactoring.

No errors have been thrown. My tests have passed since I didn t have a test for such a scenario, which was found out when I accidentally kept myself logged in for much longer than expected.

Daily reality: Claude Code in one pane, Codex in another, Cursor in a third, plus a few shells. An agent stops and waits for "yes". By the time I find the right pane, 20 min gone.

Just me? What's your setup notifications, layout tricks, or you've accepted the tax?

It doesn't even have to be a big dramatic failures, more the small moments where something clicked and you went from trusting the output by default to double checking everything. For me it was watching an agent confidently rename a function across twelve files, then leave the original function untouched in a thirteenth file it apparently didn't search, with zero indication anything had been missed. It wasn't even a hard case, the file just wasn't in the directory it happened to grep first.
What was your moment? And did it actually change your workflow afterward, or did the trust creep back in after a week like it always seems to for me?

AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.

Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.

I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity.
It made me wonder ,what does your setup look like right now?

Our initial iteration was built from scratch using Bolt over a single weekend, and I did not have any previous experience coding at all. It worked, people signed up and even paid. Then I hired an external developer to implement a feature I could not build myself and his first question was about "the schema". I did not understand what it means.

It turned out that AI has created three tables that almost literally duplicated user information in three slightly different ways, and every single query worked around it instead of solving. Nothing broke for users but every subsequent development became more complicated and expensive than necessary.

I keep coming back to this idea: vibe code is basically instant legacy code.

Not because AI-generated code is necessarily bad, but because it often puts us in a familiar situation: the system works, yet no one fully understands how it works. That makes me wonder whether some of the most useful techniques for vibe coding are actually techniques we already use for legacy systems. For example:

• Snapshot / approval tests: capture the current output and require explicit approval when it changes.

• Characterization tests: describe what the system actually does today, regardless of what it was originally intended to do.

• Golden master tests: run known inputs through the system and compare the results with a trusted baseline.

• Contract test: protect the boundaries between components, services, APIs, events, and data stores.

• Differential testing: compare two implementations and detect where their behavior diverges.

• Test carving: observe a larger execution and extract smaller, focused regression tests from it.