Break It Like You Mean It

I can build a running system in a weekend now.

That used to feel like winning. It isn't.

When there was a developer between me and the code, "done" meant someone else had already been paid to worry. Security. Double charges. The cashier's machine sitting unlocked while she walks a guest to the door. A link meant for one car that ends up in a group chat. Someone signing in on a phone whose email doesn't match the account in the database.

I didn't ignore those problems in the old world. I outsourced the anxiety.

That's the part demo culture skips. Building with AI feels like competence. Breaking what you built feels like betrayal — until you understand that the breaking is the job.

I stopped asking whether it runs. I started asking a different question: if this is real money and a real shift tonight, how does it fail?

Not a poster on a wall about security awareness. Operator failure. There are four I go hunting for every single time, because those are the four that cost money. A ticket that closes at zero dollars because the screen believed whoever was standing in front of it. A convenience code that turns into a master key, because convenience is how master keys get made. A pairing shortcut simple enough that a hotel would print it and tape it to a monitor. A payment that lands on the card and then gets collected again in cash, because two different paths both felt finished.

Those aren't edge cases. Those are Tuesday.

AI is excellent at the happy path. You describe the podium, it builds the podium. You describe the scan, it builds the scan. You say "collect payment" and it builds a button that says Collect, and the button works.

What it doesn't feel in its bones is the valet on hour eleven. The guest who was angry before he reached the podium. The card that authorized twenty minutes ago. The night auditor closing the day at three in the morning. The person who doesn't care about your roadmap and tests other people's links for a living.

Operator knowledge isn't only how the shift should go. It's how the shift goes wrong, and what must never be possible even when everyone is rushing.

So I changed the ritual. After Claude builds, I don't celebrate. I try to rob it.

I try to pay nothing. I try to be someone else. I try to run the same charge twice. I try to use yesterday's access today. I try to make the system lie to the person standing at the curb with a phone in his hand.

That isn't pessimism. It's respect for the floor.

People still ask whether an operator can build enterprise software with AI and no developer. Wrong question. The question is whether an operator will own it, now that building is the easy part.

Owning means you don't hand your people the first version that works. You give them the one that still works when somebody is careless, or malicious, or just late for a flight.

There used to be someone standing between me and that responsibility. He's gone.

Good.

Break it like you mean it — before the guest does.

The next episode is the two-week autopsy: the one where AI confidently wasted two weeks of my life, and what it took to get them back.