Post

I've been saying for a while that we, as expert Laravel developers, are just moving a lot of our projects from rescuing bad offshore work to rescuing bad vibe code. You still need the experts.

Ed Grosvenor@gros.co

I just finished up a call with someone who had vibe-coded an error into a revenue-generating application that cost the company 6 figures in (fortunately recoverable) lost revenue. It's recoverable because two developers with a combined 40 years of experience managed to unwind the problem.

Matt Stauffer

@mattstauffer.com

One really big fun change vs. bad offshore work: We're not just rescuing bad vibe code. We're also working, with love and delight, with clients who vibe code their requirements and then ask us to make it legit/stable. This is fun!

9/1/26, 10:37 pm2 reposts10 likes

Ed Grosvenor

@gros.co

10 Jan

We are trying to get away from this approach and introducing a workflow that lets the client use AI to help shape the requirements without locking in an implementation. Otherwise, we feel a little stuck with some of Claude’s questionable decisions.

Ed Grosvenor

@gros.co

10 Jan

The problem we’ve found with “vibe then stabilize” is that we can’t possibly keep up. It takes us 5x as long to wrap our heads around what they created than it took them to create it and the backlog becomes impossible very quickly.

Matt Stauffer

@mattstauffer.com

10 Jan

Oh yah, sorry, to be clear, they're not vibe coding Laravel (well, most aren't). They're vibe coding proof of concepts or specs or frontends.

Ed Grosvenor

@gros.co

10 Jan

That’s a good approach. We are trying to operationalize that a bit for a couple of clients. AI guided requirements interview, with the current state of the app in context. AI generated wireframes, etc. Then we turn it into actionable specifications for their devs to build.