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.

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!

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.

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.

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.