The Line Between Vibe Coding and Real Engineering Is Disappearing

Simon Willison, creator of Django and one of the most respected voices in developer tooling, published something uncomfortable recently. In a post titled "Vibe coding and agentic engineering are getting closer than I'd like," he admitted that the line between casually prompting an AI to build something and professionally engineering software has started to blur. In his own work. On production code.

The post hit 785 points and 884 comments on Hacker News.

Willison used to draw a firm line. Vibe coding was for personal tools, throwaway projects, situations where bugs only hurt you. Agentic engineering was the professional version, where you bring 25 years of experience, review the AI's output, and maintain high standards. But he's noticed something happening in his own workflow. When Claude Code builds a JSON API endpoint with tests and documentation, he's not reviewing every line anymore. He knows it's going to be correct. He's started treating AI agents the way he'd treat another engineering team at a large company: as a semi-black box that produces reliable output.

This is what no-code has always been. No-code builders have been operating in exactly this mode since the beginning. When you build an app in Bubble, or configure a workflow in Make.com, you are trusting abstracted systems to produce working software. You don't inspect the generated code. You can't, usually. Instead, you specify what you want, verify it works, and iterate when it doesn't. That's the same workflow Willison just described for his production engineering. Prompt, verify, ship.

The next time someone tells you that building with no-code tools isn't "real" engineering, point them to Simon Willison's blog. One of the most respected developers alive just admitted his production workflow looks increasingly like what no-code builders have been doing all along.