Vibe coding got us here. Anyone with Claude and a good prompt could ship something real in a weekend. That was the unlock. That was the magic.
But somewhere between the prototype and the production deploy, the magic became a liability. Shadow Resend accounts. Stripe pushes that would've undercharged customers. Cron endpoints curled without permission. Repos with no review process. Databases with no access control.
The same fluency that lets us build fast lets non-engineers ship code that handles other people's money and data — without the guardrails every real engineering team takes for granted.
In this lightning talk, I'll make the case that the era of vibe coding as production strategy is over, what comes next looks a lot like two-person review and Amazon's STL framework, and why the operators who survive the next two years will be the ones who can tell the difference between prototyping and shipping.