I've been thinking about something. We've gotten really good at using AI to generate working code, but we're not treating it like production code in terms of documentation.
Traditional developers spend significant time documenting their code because they know future them (or their teammates) will need to understand, modify, or debug it later. But with AI-generated code, we often just copy-paste and move on.
One for chatbot templates in 2018 that was used by 700+ marketing agencies.
Another in 2020 for job seekers in the U.S., which reached 5.5M users.
So let s suppose I have some experience. You can read about me on Bootstrappers, TechCrunch, Dev to.
Now I m considering building a marketplace where creators can list their vibe-coded projects along with the code, a live demo link, etc. The idea is to target:
I'm spending $200/month on Claude Code. Normal, or am I nuts? How much are you really spending? What tool is worth every penny, and what's way overrated?
Poll: How much are you spending per month on vibe coding tools? Options: $0 $50, $51 $100, $101 $200, $201+
Hello everyone, I am dabbling in "Vibe Coding" and wanted to know if anyone has any advice or best practices? I have used Cursor for a while, but have just started to use Claude Code to take a more hands-off approach. I am liking it so far for getting the general layout and functionality, and then I go in to clean up and finish the work. I have also used some MCPs, but I am looking for more! All advice is appreciated. Thanks in advance!
I m curious! How do you document the different iterations of your app so you can revisit them later for enhancements or debugging?
Do you stick to traditional docs, use wikis, or something more creative?
As a solo dev, my app is getting bigger and more complex with multiple automations and moving parts, and I often struggle to remember all the implementation details. Do you also save the prompts you used to develop certain features, or have your own system for keeping track?
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).
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.
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?
