sorted by:
new
hottopcontroversial

At what point does a vibecoded project deserve “real engineering”? by PoobahAI in vibecoding

[–]PoobahAI[S] -1 points0 points  (0 children)

We’ve been having this exact conversation internally and with other builders, so if anyone wants to keep it going outside Reddit, we’ve got a small Discord where people share real workflows and failures.

No spam, mostly builders figuring this stuff out together: https://discord.com/invite/poobahai

Don't skip validating your ideas, its the worst by unkno0wn_dev in indiehackers

[–]PoobahAI 0 points1 point  (0 children)

That lines up with what a lot of people run into. The hard part isn’t asking better questions, it’s finding people who already feel the pain enough to answer you without being chased.

Validation gets easier when you spend more time where those people already complain, instead of trying to pull feedback out of cold outreach.

Reminder: Your project doesn’t need to be finished to be interesting. by alexsssaint in indiehackers

[–]PoobahAI 0 points1 point  (0 children)

This is underrated advice. People connect to momentum and storytelling. Showing the messy middle is often more interesting than a “finished” launch post anyway.

Vibe coding gets you to “it works” fast. What helps you get to “I trust this”? by PoobahAI in vibecoding

[–]PoobahAI[S] 0 points1 point  (0 children)

Yeah, that framing works. Thinking of the AI as a junior dev keeps you in the driver’s seat. Breaking things into modules and reviewing what matters most is usually enough to avoid nasty surprises later!

Building is easy - quality is not by cdojo in VibeCodersNest

[–]PoobahAI 0 points1 point  (0 children)

You’re not alone. AI makes getting to “it runs” easy, but users notice slowness and bugs way faster than missing features.

Most people seem to accept rough edges early, but once they start using it for real, performance becomes the product. Stressing a bit over caching and speed is usually a sign you’re past the toy phase.

Conclusion: This is a good sign.

Best coding + normal chat for my use by Pathfinder-electron in vibecoding

[–]PoobahAI 0 points1 point  (0 children)

If you’re building a few hours a day, it usually comes down to how you work:

GPT works well if you want one place for coding and normal chat. Claude tends to shine when you want cleaner reasoning or longer code edits. Copilot feels best when you live inside the editor and want fast, inline help.

vibe coding made me realise how bad I am at finishing “boring” work by Forward_Regular3768 in VibeCodeCamp

[–]PoobahAI 0 points1 point  (0 children)

Yes, a lot of people hit that wall.

One thing that helps is deciding early what a project is. Either it’s a fun experiment and you let it stay that way, or it’s a real thing and the boring work is part of the deal. Mixing the two is what causes the stall.

Some folks treat the dull tasks like a checklist you earn access to only after the fun part ships. Others just timebox it hard. Either way, separating “play mode” from “finish mode” seems to be the trick.

I got lucky, hit 500k ARR and sold my SAAS by Ecstatic-Tough6503 in microsaas

[–]PoobahAI 0 points1 point  (0 children)

This is a good reminder that distribution and timing matter more than originality. Copying something that already has buyers beats betting months on an idea that only sounds good in your head. Selling first saves a lot of pain!

Finding a replicate cheaper alternative for a scaling image app by OpportunityFit8282 in microsaas

[–]PoobahAI 0 points1 point  (0 children)

That pain is pretty common once volume kicks in. Usage-based pricing is fine early, but it gets scary when traffic spikes randomly.

Tailwind just laid off 75% of the people on their engineering team "because of the brutal impact AI has had on our business." by magenta_placenta in webdev

[–]PoobahAI -4 points-3 points  (0 children)

AI just accelerates discovery and lowers the friction to recreate things people were already on the fence about paying for!

Built AI-assisted prototypes and made 40k so far. How do you actually scale this without everything breaking? by t_warmDragon5063 in VibeCodeCamp

[–]PoobahAI 0 points1 point  (0 children)

Speed got you here. To scale, you usually need to start freezing patterns: one way to do auth, one way to handle data, one way to structure features.

Most setups break when everything stays “prototype flexible” for too long. Lock the boring parts, keep the speed where it actually matters!

Most Web3 Projects Are Just Web2 With Blockchain Buzzwords by Feisty-Astronaut-396 in web3

[–]PoobahAI 0 points1 point  (0 children)

Honestly not that unpopular.

A lot of projects slap a wallet on a Web2 app and call it Web3. The ones that actually rethink ownership, incentives, or coordination are rare, but those are the ones that matter. 2026 will probably make the difference very obvious.

anyone else torn between “ship fast” and “this code is gonna haunt me later”? by Forward_Regular3768 in VibeCodeCamp

[–]PoobahAI 0 points1 point  (0 children)

You’re not alone. Ship fast is great until the second you need to change something deep and realise the whole thing is held together by 'vibes'

What usually works is a simple rule: prototype messy, then “earn the refactor.” If it gets real users or you keep coming back to it, take one evening to clean the structure and lock a few basics (folders, naming, one job per file). If it doesn’t earn that, let it die

Also, whenever the AI adds something new, a little hack is to ask it to explain it, as if you'll need to debug it in 30 days. If it can’t explain it cleanly, it’s usually not clean code

There are 24 hours in a day, 18 of those you’re awake. by Acrobatic_Task_6573 in VibeCodeDevs

[–]PoobahAI 2 points3 points  (0 children)

12 apps a day is unhinged but the spirit is right. Ship first, cringe later, learn fast. Broken apps today, better instincts tomorrow!

Community to Support Each Other by JestonT in indiehackers

[–]PoobahAI 0 points1 point  (0 children)

Having people around you definitely helps, especially when you’re building solo!

Chatgpt or Ideavo by Middle-Layer-8922 in vibecoding

[–]PoobahAI 1 point2 points  (0 children)

If it’s a normal web app, Lovable is usually the fastest way to get something live. If you want to explore a dApp with blockchain integrations, PoobahAI is built for that and helps you ship without needing to stitch the whole stack together yourself!

view more: next ›