A founder spent six weeks with AI tools and shipped 300,000 lines: a WhatsApp clone with real users and a polished UI. Underneath, security holes, queries that pull an entire table to count its rows, and a codebase three senior engineers couldn't untangle. With low-code the limit was visible: the blocks ran out and you called an engineer. Vibe coding has no visible wall. Nothing stops you, nothing warns you, until production. He never saw the line he crossed.
The constraints didn't vanish, they shifted: security, maintainability, performance, UX. The AI generated with a weak feedback loop: generate, glance, ship. Exploration is real value: you have to build things to understand what you're building, and AI makes that faster than ever. So I'll rebuild it the other way: hand the AI the instruments engineers spent years mastering, as a tight loop it answers to while it writes. Constraining AI before it writes, not after, is what I call Human-Driven Development.
Tooling only goes so far: it raises the floor and can't make the judgement call. The hard skill is catching the moment a prototype gets run as a product, bearing load it was never designed for, and humble enough to get a real review first. Drawing that line is what separates a product from a rewrite.
I'll run both loops on the same work, generation after generation, and you'll watch them diverge, my AI sidekick Loyal calling out what's rotting, or holding, underneath. AI made the engineer the last line of defense.
This talk has been presented at AI Coding Summit Berlin, check out the latest edition of this Tech Conference.
