Vibecoding
p/vibecodingBuild for the vibe, debug later
trending
•

9mo 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:

•

1yr ago

Top 3 Vibe Coding Tricks

What are your top tricks or techniques when building apps and other digital experiences with AI?

The foundation of any successful collaboration, whether human or digital, is mutual understanding and shared context. When onboarding a new developer, you provide essential information about the project's architecture, technology stack, coding conventions, and goals... we can call it "vibe coding" all we want, but to be effective we need more than just vibes.

•

8mo ago

Why we killed our 430-line Orchestrator (and why yours might be a "Black Box")

I ve spent the last few months obsessed with a specific failure in multi-agent systems: The Black Box Dilemma.

Most MAS setups I see (including my own v1) treat orchestration as "glue code." You have a central manager, a few agents, and a lot of hidden logic. When it fails, you re left guessing. As someone on IndieHackers put it: "You re just parallelizing chaos."

The Shift: From "Dictator" to "Blackboard"

In our latest iteration, we deleted the 430-line monolithic controller. Instead, we implemented a Blackboard Pattern.

Burned $250 in tokens on Day 1 with OpenClaw

When I first set up OpenClaw, I ran into a big problem immediately.

I spent $250 on my first day doing what felt like harmless testing.

Nothing production. No customers. Just me trying things like:

  • Summarize this Slack thread

  • Give me a morning digest

  • Explain this error log

  • Pull action items from the last N messages

  • A couple Telegram alerts

I got tired of waiting for Anthropic to unify its UX

So I've got a bunch of agents building Klatch for me now, following Gall's law principles. It's still in alpha. No overpromising. But I got it going this past Saturday and it's already functional. Like most of my stuff this is fully open source so anyone can grab it and fork it, or make a version for Gemini, or whatever.
Let me know if you find it useful. We're working on context and resource preservation post-import, next.

•

9mo 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.

•

10mo ago

What’s your current no-code + AI stack for building SaaS in 2025?

AI and no-code tools are evolving insanely fast right now. Every few weeks there s a new tool that changes how quickly you can go from idea to product.

I ve been experimenting a lot with different vibe coding platforms lately, trying to find the right balance between speed, control, and flexibility. What s surprised me most is how far you can go today without a traditional engineering setup.

For context, I recently built @Sendrise , an all-in-one cold email outreach platform, using a no-code + AI stack. I used @Lovable for building the product flows and UI, combined with AI tools for writing, automation, and logic. What started as an MVP quickly turned into a fully working product with lead management, campaigns, CRM, and analytics.

•

9mo 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.

•

10mo ago

Vibe coders: how do you catch bugs before they hit production?

Building my app with AI tools, zero coding background. The magic part - I can ship features in hours. The scary part - I have no idea if the code is actually good.

Right now my "QA process" is:

- Does it work when I tap around?

- Did anything break that worked before?

•

9mo 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.

First
Previous
•••
545556
•••
Next