I've been letting Claude/Cursor do most of the typing lately and I noticed I stopped double checking what actually goes out in the API calls. then last week I caught myself pasting a real customer row into a prompt just to debug faster.

anyone else have a moment like that? where the vibe coded thing had a hole you'd never have shipped if you were writing it slower. secrets in a log, some data you didn't mean to send anywhere, whatever. My product is focusing on this and I would like to know is this a serious issue?

I m noticing something weird happening in solo dev land.

We used to compete on:

• remembering docs

• knowing frameworks

• being a better coder

Now it feels like the real edge is:

Finally showed my cofounder's technical friend the app I'd been building solo with Claude Code for two months. I was proud of it, it worked, users were paying for it, I felt like a real founder walking him through the codebase.

He got quiet about four minutes in. Not rude about it, just quiet in that specific way where you can tell someone's recalculating their opinion of you in real time. Eventually asked why there were three different ways of handling API calls scattered across the codebase, and I didn't have an answer beyond "that's probably just whatever the agent decided each time I asked for something new."

Didn't feel great. The app still works, still makes money, still solves the problem it was built for. But something about watching someone who actually knows the craft better than me raise an eyebrow at it made me feel like a fraud for about a week, even though nothing about the product itself had changed.

Has this happened to you, showing your vibecoded work to someone with real engineering chops? What did they catch that you'd never have caught yourself, and did it actually change how you build going forward, or did you just quietly feel bad about it and move on like I did?

I like how fast vibecoding makes it to build, test, and patch things. A lot of product bugs that would have taken hours now disappear in minutes.

But I still hit a different class of bugs: the ones where the code is technically fixable, but the product decision is not obvious.

Should this edge case be handled in the UI or the backend? Is this a bug, or a missing product rule? Should the agent patch the symptom, or stop and ask what behavior we actually want?

That is where vibecoding gets interesting to me. It is not just about whether AI can write the fix. It is about whether we know what the right fix should be.

Noticed lately that most of my prompts to Claude Code or Cursor aren't new instructions, they're me re-stating stuff that was true 20 messages ago and got lost: which file owns this logic, why we chose this pattern over the obvious one, what NOT to touch. Feels like half my typing is context restoration, not task description.

Curious how others handle this. Do you keep a running "state of the project" doc you paste in, rely on the agent's own memory/context features, or just accept the repeated overhead as the cost of doing business? What's actually cut it down for you, if anything has?

not talking about the obvious stuff like "don't rm -rf prod", more the gray area tasks where the agent is probably right but you still want eyes on it before it goes out.

for me it's anything that changes a pricing table or a billing calculation. I'll let an agent refactor half my codebase overnight, but the second a PR touches how much someone gets charged, I read every line myself even if the diff is three characters. one off-by-one there and it's not a bug report, it's a support ticket and a refund.

Live Feb 28th, 9am PT - drop your questions!

Hi everyone,
CEO of Bolt here! Super excited to open up about our journey and offer any learnings and stories I can to help other makers on their journey. Within a span of 2 months we've grown to $20M in revenue and were recently featured in NYT as paving the way for vibe coding.

Hey p/bolt-new community,

I recently started building Couples Hub (https://coupleshub.io/) a React-based application and Next.js based landing page using Bolt.new. Couples Hub is a product of my hobby brand "MD Meets Techie" which I've run for the past four years, creating digital products specifically for couples. Given my technical background, diving into Bolt.new was kind of a fun experiment (esp given how drab and boring my day job is). I noted several challenges along the way and I thought I'll share a few tips on what I've learned thus far. 

I'm a veteran and solo founder with no formal coding background. Spent the last few weeks directing Replit's AI agent (with Claude as a strategic/QA partner) to build a real production app, entirely from my phone.

The part that surprised me: the "vibe" is the easy 20%. The other 80% was the same discipline any build needs catching bugs by hand (missing auto-capitalization, a timezone off-by-one, a file upload limit rejecting real phone photos), refusing to accept "it's fixed" without proof, running full walkthroughs section by section, chasing root causes instead of patching symptoms.

That's made me rethink what "vibe coding" even means. It's not skipping the engineering discipline it's relocating it. Instead of writing code, you're writing precise instructions, reviewing output critically, and doing QA like a hawk. If anything it demands more discipline, not less, because you can't rely on catching mistakes by reading your own code you have to actually test everything.

For others who've directed an AI agent instead of hand-coding: has your experience matched that, or did you find a different bottleneck? What ended up being the hardest part for you the instructing, the reviewing, or something else entirely?

Built my app with Lovable a few months ago. Launch went fine but since then I've had three separate production issues; auth breaking, database timeouts, a webhook that silently fails. Each one took me days to figure out and I have zero engineering background.

Curious what others are doing. Are you just patching it yourself, hiring freelancers each time, or has anyone found something more ongoing? I've been wondering if a monthly retainer for this kind of support would actually be worth it or if that's just me.