I don't know if this works for everyone or only for me. First of all, I think when AI coding tools first became popular, the biggest excitement was that anyone could build software without years of programming experience. But after experimenting with these tools, I think the hardest part has shifted. Writing prompts is becoming easier. The real challenges are:
Knowing what to build
Turning an idea into a product users actually need
Debugging unexpected problems
Making the app reliable enough for real users
AI can help you create a prototype quickly, but building a real product still requires product thinking, iteration, and understanding users. I m curious about people who have used AI coding tools to launch something:
What was the biggest bottleneck after your first version was built?
Real question for anyone running coding agents daily.
I started counting how often Claude Code and Codex ask for permission during a typical session. It's around 100 prompts per hour. Read file? Yes. Run test? Yes. Lint? Yes. git push --force? Also yes if you're zoned out.
While building out Aiden's keyboard input handling, we hit something strange: modifier-key shortcuts (Cmd+V, Cmd+A, Shift+X) would intermittently fail on iPhone, while plain letters typed fine every time.
Took a proper controlled experiment to isolate it, keyboard-only setups worked 32/32, adding a mouse brought the failure back, removing it again fixed it, 22/22 clean. Turned out iOS was routing the command to the wrong place (SpringBoard, the home screen process, instead of whatever app was actually open) whenever AssistiveTouch was on and it saw both a keyboard and a mouse connected. We confirmed it's not specific to our hardware, it reproduces on a totally unrelated gaming keyboard and a Bluetooth keyboard too.
Our fix switches Aiden to a keyboard-only USB profile right before any modifier-key action, then restores mouse capability after. Workaround, not a real fix (that's on Apple's side), but it works reliably now.
Is it truly vibe coding if there aren't tunes making the vibes...well...vibey. Thought it'd be fun to put together a YouTube playlist of what everyone listens to when building! I'll take all the links and make a playlist on YouTube after a couple of days :) Just drop the link and tag the tool that you mostly use. I'll start! I vibe with Black Coffee and mostly use @Cursor!
Scaffolding frontend layouts, Tailwind components, and basic CRUD forms through natural language prompting is remarkably smooth now.
However, once an app requires dynamic, competitive state like handling real-time bids, managing race conditions when two events trigger simultaneously, or verifying payment webhook signatures pure conversational generation starts hitting walls.
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.
As a data engineer who has little experience in full-stack software development, I ve been experimenting with vibe coding tools to move fast in the early stages.
My flow looked like this:
Prototyped the main UI in V0 (after 300+ iterations/conversations back and forth)
