I often vibe code and later realize I m fatigued just trying to remember what I actually worked on. Looking back at commits helps, but I tend to break them up a lot, so it s not the full picture.
Tools like Jira, Linear, or whatever else feel like they lag behind the reality of coding. Updating tickets takes more time than the coding itself.
Anyone else feel this pain? How do you keep track without killing the flow?
I m a PM, and I ve been prototyping more and more in Lovable/V0 lately it s quickly becoming my default sketchpad for product ideas. One challenge I keep running into when sharing with stakeholders: how to present different variations of the same prototype. It feels like today s vibecoding tools don t yet have the equivalent of feature flags, a simple way to toggle between ideas within one prototype. I m curious how others approach this. Do you fork? Keep multiple versions and restore as needed? Or is there another workflow I should try?
I m looking to connect with people who ve used vibe coding to build and launch a product that s already monetizing. I want to chat about the challenges we face when building (and scaling!) vibe-coded apps and products - from security issues to unexpected bugs to UX problems.
The plan is to write down and share the insights from these conversations, so we can all learn from each other s experiences.
If you ve been through it, I d love to hear your story :)
I wanted to see if Gemini s AI app builder could handle something real. I needed a fast way to generate estimates without paying for a clunky CRM, so I built a simple tool called QuiqEst. It takes natural language and spits out a clean, downloadable estimate or invoice.
It actually works but what I m more curious about is: has anyone else here built working tools with Gemini? Did you hit any limitations or cool breakthroughs?
We just completed a full security upgrade for our SaaS platform
The journey wasn t easy. Damn, I suffered such much along the way! We broken builds, lockfile chaos, and dependency nightmares... but we came out stronger:
As a data engineer who has little experience in full-stack software development, I ve been experimenting with vibe coding tools to move fast in the early stages.
My flow looked like this:
Prototyped the main UI in V0 (after 300+ iterations/conversations back and forth)
AI coding tools seem to come in two main flavors: IDE-based, like @Cursor and @GitHub Copilot, and terminal-based setups, like using @Claude Code to generate commands, scripts, or entire files. Both have their fans, but which one actually helps you move faster?
Curious what flow people are sticking with long term, and where you see the most gains (or frustrations).
I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team? My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product. I'm curious what you all think, would you hire a vibe coder?
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.
