Post
Indeed, I don't think there's much distinction between "agnetic engineering" and "vibe coding" either. https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/
The incentives of high output generation with review being the bottleneck will clearly move users towards just vibing and less reviewing. (But that has seemed obvious to me for a long time, anyway)
@cwebber As it has already been put before: making more code of lower quality had never been a bottleneck.
The incentive to skip review is real, but it doesn't erase the distinction. "Agentic engineering with careful review and tests" is a discipline; vibe coding is skipping that step. The problem isn't the tooling, it's whether you treat review as optional.
@cwebber “it’s the same picture”
@cwebber Time to make agentic automation scalable and that is our key focus of 2026 /s
@cwebber I agree with the blog post that "agentic" isn't much of a middle ground. But I don't think FOSS needs to compete with enterprise head-on in terms of code volume. We've always found ways to punch above our weight and should think harder about this.
Anyone who is pushing FOSS projects to embrace AI based PRs with thorough review should be thoughtful that this logical endpoint will come to their beloved FOSS projects also.
@cwebber Willison's distinction (and previous iterations of it) strikes me as dangerously naive. Based on my own experience with both the tool and, y'know, human nature, nothing but the most draconian guardrails will prevent people from taking the easy way with these tools.
We were never going to do this safely.
@mttaggart @cwebber I think "naive" is being overly generous here. The phrase "responsible use of AI to write code" is slipping a hell of a lot of unevidenced and extraordinary claims in — I read that post as yet more boosterism.
We should reject slop in OSS, whether it's branded as "vibe coding" or "agentic engineering," and following the same ethical imperatives.
Install bonfire.cafe
Get the full app experience
