The @v0 by Vercel team recently dug into industry trends to publish the first State of Vibe Coding report.

My key takeaways:

1. Everyone can build: 63% of vibe coding users are non-developers, generating UIs (44%), full-stack apps (20%), and personal software (11%).

2. Adoption is everywhere, with significant adoption rates in APAC (40.7%), Europe (18.1%), North America (13.9%), and LATAM (13.8%).

3. 92% of US developers use AI coding tools every day

4. 30% of new code at @Google is generated by AI

5. 25% of @Y Combinator startups rely on AI-generated code

6. Rapid expansion has a cost. Vibe coding apps keep hitting vulnerabilities: exposing secrets, access misconfigurations, hardcoded credentials.

7. The future: going mainstream or hitting its sweet spot in working MVPs, the vibe coding trend is here to stay, and it's happening now.

I ve been spending more time vibe coding recently, and I ve started to question something I initially took for granted. Most of the conversation around vibe coding is about speed. Like how quickly you can go from idea to prototype, or how fast you can iterate. And to be fair, that part is real. The barrier to building has clearly dropped.

But the more I use these tools, the more it feels like speed isn t the limiting factor anymore.

The real constraint seems to be taste.

• what do you choose to build?

• what do you keep vs discard?

• what actually feels right vs just working ?

• what is genuinely useful vs just impressive in a demo?

I used to plan my lunch breaks around AI tasks. Pick the one task that's easy enough to just hand off, start it, go eat.

Came back more than once to find the agent had stopped two minutes in over some dumb question. Not even a permissions thing, it just sat there waiting for me to say "go ahead". Didn't even know it was stuck until I checked.

Over the last few months, AI-assisted coding and "vibecoding" have significantly changed how quickly I can prototype and ship ideas. Instead of spending hours setting up boilerplate code, I've been focusing more on product logic and user experience.

However, maintaining code quality and debugging complex workflows can still be tricky when relying heavily on AI agents.

I m curious about how other builders in this community are balancing speed and code quality:

What does your primary AI tool stack look like right now?

Non-technical founder here, built my whole product with Claude Code. Everyone in this forum keeps saying the same thing UI and analytics get the "looks fine, ship it" treatment, but billing and auth get the paranoid line-by-line review. I've lived that.

Here's the twist though: my product IS the billing edge case. It's a tool that recovers failed subscription payments, so the entire thing lives in the messy world of declined cards expired cards, insufficient funds, bank 3-D Secure/SCA challenges that all look similar in the data but need completely different handling. Vibe-coding something where a wrong branch means someone gets emailed "your card was declined" when it actually went through was genuinely terrifying. I couldn't just trust the vibes.

honest self-assessment time. when an agent finishes a task and shows you a diff, what actually happens?

for me it depends entirely on the size. under ~30 lines I read every line. past that I mostly skim for anything that touches auth, payments, or migrations and trust the rest if tests pass. I know that's not a great policy, it's just the realistic one given how much code moves through these sessions in a day.

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've shipped work where 90%+ of the code came from prompting an agent, with me mostly reviewing, testing, and directing the architecture. Never explicitly disclosed that to the client, they just know it got done fast, works well, and stayed in budget.

Is that dishonest, or is it no different from using a framework, a library, or a junior dev and not itemizing every line's origin? Nobody used to ask what percentage of a website a developer typed themselves versus copied from Stack Overflow or scaffolded with a generator.

But this feels different somehow, maybe because the speed and volume are so much higher, or because "AI-written" still carries a stigma that "used a library" doesn't.

Where's your personal line? Do you disclose upfront, stay quiet unless asked, or does it depend entirely on who's paying and what they'd actually do with that information?

Hey PH family.

Been part of this community for years now, and if there's one place to talk with builders, this is it.