Graham McNicoll

Amazon just held a mandatory meeting after vibe-coded changes caused multiple major outages. This story is going to repeat itself across a lot of engineering orgs. AI coding tools are genuinely impressive. I use them every day. Here's what needs to change, before AI-generated code touches production. Wrap every feature in a flag. That flag is your kill switch. The moment something breaks, you turn it off. No rollback. No emergency deploy. No six-hour outage while the team scrambles. Vibe coding without feature flags is inherently risky. You are moving fast with no ability to control what happens when the code goes wrong. The real question for your engineering org in this new way of building product is whether you have the infrastructure to turn off features when something goes wrong. Can you detect errors fast enough before real damage is caused? Can you do this automatically? If your team is shipping AI-generated code directly to production, send me a DM.