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.

I built a whole SaaS landing page with auth and pricing in one prompt and felt like a genius. Showed everyone, tweeted about it, the whole thing.

Then I went back to fix one small bug- the signup button. Instead of just fixing it, the AI assumed I meant a completely different button and changed that instead.
When I corrected it, it "fixed" the issue by rewriting a chunk of the auth logic I never asked it to touch- and broke login entirely in the process.
By the time I pointed that out, it had made three more assumptions to "fix" its own fix, and none of them matched what I'd actually built two hours earlier.

I ended up scrolling back through the entire conversation trying to reconstruct decisions I'd already made, just to get back to square one.

Has anyone actually found a real fix for this, or is everyone just quietly rebuilding the same project for the fifth time?

Been using both for about two days now, and I feel like Fable 5 is actually performing better than Fable 5.1 for me. Orchestration and correctness feel noticeably stronger on Fable 5. Is anyone else seeing this, or is it just my use case? Curious to hear how others are experiencing the two models so far.

I have been observing numerous posts on social media about just vibe coding your applications and sell it to the client or launch it, People actually ignore the technicality of saas products.

I just want to know from them -

• What about database and its schema, how are you going to store data?

• What about application security?

• What about if you have to just add a new button in your page, are you gonna just ask the AI by pasting the whole code?

• What about scalability of the application?

• Are you sure, your application is not breaking from anywhere?

I'm what you might call a gringo vibe coder.

No dev degree. No traditional background. Just me, Cursor, Claude, and AI... figuring things out together.

Rick Rubin said it best: "In the past, for music, you had to go to the conservatory and study for years... then when punk rock came along... if you had something to say, you could say it." He calls vibe coding the punk rock of coding.

about to Launch a product for creators after building for a few weeks to months.
Started as a way to get into vibe coding and just got real useful real quick lol.
But the goal is still that - mix my skills and knowledge as an engineer with the good parts of AI coding.
So i learned a few of what to need and have

• Claude.md file

• best coding practices section

• pretty heavy compartmentalization & file structure separation

• certain ways to prompt

• ask for implementation plan before telling it to code

But i feel like all i learned is about directing prompts - im wondering...

what are you guys finding are the best .md or deeper ai vibe coding tricks that are helping you save time? be more efficient? debug ai less or help it get it right the first time? whats your vibe code tips and tricks?

A products fetch in my iOS app came back empty. No error, no crash, nothing unusual in the logs. The purchase button simply sat there greyed out, because an empty list is a perfectly valid response and every check I had passed on it. App Review found that one and I had not.

The pattern is a call that fails without failing. An empty result, a stale cached value, a permission that was denied months ago and now returns nothing instead of an error. The user is stuck and the code is behaving exactly as written, which is why an agent cannot help much either. Ask it to reproduce the failure and it writes a test that agrees with the current behaviour.

I've noticed my workflow has completely inverted over the past year. I used to sit at my Mac typing code; now Claude Code or Cursor does the long stretches, and my job is the interruptions: it stops, asks "should I refactor this or keep the interface stable?", and waits until I answer.

Which means I'm chained to my desk not by the work, but by the questions. Walking back from the kitchen to type "yes, option 2" feels absurd.

Curious how everyone else handles this:

I'm a senior developer in Seoul. My commute is long and the subway is always packed. Here's how I tried to make mobile development work and where it fell apart.

Seoul subway is not quiet. You're standing, one hand gripping a bag, the other holding your phone. Coding the traditional way IDE, terminal, file trees is physically impossible. The screen is too small, your fingers too fat, and the text too tiny to read without squinting.

---

The problem in a nutshell:

With AI writing the majority of first drafts now, I've noticed something shifting in how engineering teams work, the bottleneck isn't writing code anymore, it's reviewing it.

A few things I've been thinking about:

• Most devs I know got good at coding by writing a lot of it. But we never really trained to read it the same way.

• Code review culture is getting worse, not better, as AI output volume increases. People are rubber-stamping PRs they don't fully understand.

• The bugs that make it to production aren't from bad writers, they're from missed reads.

Curious if others are feeling this. Do you actively practice reading code, or is it just something you pick up passively? Has AI changed how carefully you review code before merging?