Vibecoding
p/vibecodingBuild for the vibe, debug later
trending
SANKET SARKAR

2mo ago

How I built an internal compliance tracking tool?

I didn t build our internal compliance tracking tool the traditional way.

I vibecoded it.

Instead of long PRDs, heavy sprint planning, and weeks of back-and-forth, I stayed close to the problem and built in tight feedback loops shipping small, observing behavior, and iterating fast.

The flow was simple:

Max Musing

3mo ago

The vibe coding trap

There's a popular narrative on social media right now that AI can build software so quickly and cheaply that SaaS is dead (or will be soon).

Why pay for Linear when AI can build a project tracker in an afternoon? Why pay Stripe $30k/year when you can vibe code your own billing system in a weekend? The cost of building software has collapsed to near zero, therefore the value of selling software has collapsed to near zero. QED, SaaS is dead.

Cheng Ju

6mo ago

Which BaaS works best for “Vibe Coding” projects — local-first, fast to deploy, and low-cost?

Hey everyone

I m exploring different Backend-as-a-Service (BaaS) options for vibe coding projects small but creative builds that start locally and later go live (think quick prototypes, coding agents, or AI-powered hobby apps).

I d love to hear your thoughts on:

  • how easy is it to debug or simulate the backend locally?

  • how smooth is it to go from local to hosted?

  • any gotchas or scale-to-zero tricks to keep costs minimal?

  • functions, auth, storage, DB branching, edge runtimes, etc.

Hoa DO

3mo ago

Can a Product Manager ship a real website end-to-end today without handoffs?

This was a deliberate experiment inspired by my CTO. I wanted to test a simple question:
Can a Product Manager ship a real website end-to-end today without handoffs?

Here s the stack:

  • @Figma structure, hierarchy, & visual components

  • @Adobe Illustrator brand consistency & visual components

  • @ChatGPT by OpenAI positioning, copy angles, objections

  • @Lovable iterate layouts before committing

  • @Cursor turn ideas into real UI fast

Will Wei

11mo ago

Almost Leaked My Key—Thank God for GitGuardian

This morning I opened my inbox to find an alert from GitGuardian about a leaked key. My first thought: Great, another phishing email. Nearly deleted it on the spot. Then I realized yesterday when I was using Cursor to bulk-update my scripts, I d left the API key in plain text

Furqaan

11mo ago

Do you predict people will actually watch AI-generated films?

Here's an idea we are thinking about:

Netflix for AI generated fims, pretty self explanatory

Problem

This week, Google unveiled Veo 3, its latest AI video model capable of generating hyper-realistic videos from text prompts. The line between AI-generated and human-made content is blurring rapidly.

DHxWhy

3mo ago

I burned 15B tokens in 3 months. Had nowhere to record it—so I built one.

Hey everyone

No CS background. Started vibe coding 3 months ago.

16+ hours daily. 15 billion tokens later I'm still learning.

I was using a Claude Code leaderboard service made by another dev.
Submitting my daily stats became my end-of-day ritual. It was my fuel for vibe coding.

Pravin Boppuri

6mo ago

I Built my SaaS Using Vibecoding (and Why I Chose Claude Sonnet 3.5)

I just launched AllPub.co and built pretty much the entire thing using Vibecoding with Claude Sonnet 3.5. I'm a software architect with just some basic Python knowledge, so this was my first full web app build. Wanted to share my experience!

What I Built

Gauthier

3mo ago

Why semantic search failed our AI memory system (and what we replaced it with)

Hey everyone, been a Product Hunt visitor for years but never signed up, so I thought I'd start by sharing some recent learnings that hopefully other builders will find useful.

For context, we're building FanBase Copilot, an AI assistant for content creators that learns their voice and context over time. The memory layer is critical. It's what makes the AI actually useful after the first conversation.

Mihir Kanzariya

3mo ago

Hot take: AI isn’t forgetting. Your workflow is.

Every vibe-coding session starts the same:

Here s the context again
Here s what I already tried
Please don t repeat this

That friction killed my flow, so I built Blocpad (CLI).

It keeps context with the project, not trapped in chat history tasks, decisions, notes, all local.
AI reads the state. No re-prompting.