[TheGRS]

My take at this point is that everything is still too fresh to really settle on some new paradigm for working. Yegge is clearly very passionate about this, and that's what got me to try his book. I just don't think he can really articulate some strategy to it yet.

To answer your question, no. I'm growing deeply suspicious of outright vibe coding as a practice. We still need to figure out the tools and process, so experimentation is pretty much where we're still at.

[hedgehog]

I have some practices that seem to be very effective but I wouldn't call them "vibe coding" and they're not really exciting enough to write a blog post about. Mostly: code is cheap, review labor is not, write down your process and make templates for all the documents in it (pretty much implementation plan, commit message), make sure the agent keeps a log of everything it's done and why (so it doesn't repeat work), periodically improve the process by instructing the agent to review your session transcripts and pull request comments for ways to make the process more reliable and efficient. The amount of tool churn in this world is pretty funny.

Edit: One concrete thing that the robo coding changes is it's totally reasonable to have the tools synthesize requirements based on a Slack thread, write a design doc, polish that, do a draft implementation, and then finally open a ticket to do the work with the benefit of having tested many of the assumptions.