I spent most of my career doing non-technical work, and I now build our product, @HeyNews. I got there by talking to AI coding agents night after night. The catch: the agents are good company right up until 4am, when you're still hitting approve every thirty seconds and what you actually want is sleep.

So I built a loop I can walk away from and wrote up exactly how it works: https://blog.heynews.co/afk-codi...

I ve noticed that my workflow has changed completely over the last year. I rarely start a new project with a blank file anymore. Instead, I pick a template, reuse snippets, or let an AI helper suggest the structure and then I just vibe my way through the build.

It s faster, but sometimes I miss the old blank screen energy, when every line felt handcrafted.

I m curious how others here approach it:

Do you still prefer to build from scratch?

disclaimer: I'm not an engineer. i do growth and marketing.

when people talk about vibe coding they usually mean shipping a product. an app, a saas, a tool with real users. that's the version that gets posted. but it's not where things actually changed for me.

Vibe coding tools have been making huge improvements, but things can always get better.

What blockers are you still running into? What has no one solved yet? What do you wish you could do, but can't yet?

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.

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.

CLI coding agents killed my IDE anyone else?

Genuine question: since CLI-based coding agents became a thing, how many of you have actually stopped opening your editor?

Hey PH family.

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

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:

Stack settled into this after breaking it a few times:

Cursor for IDE work. Claude Code for longer agentic runs when I trust the spec. Codex for boring tickets while I'm in meetings. v0 when a client needs a UI mock in 10 minutes.

The thing that actually changed how I use all of it: stopped treating them as interchangeable and just routing by task type. Refactors go to Cursor. Full feature from a spec goes to Claude Code. Tedious backlog stuff goes to Codex.