The 1991 Workshop Siren: Why Practical Architecture Always Beats "AI Theatre".

Igor Pogany’s recent breakdown on "AI Theatre"—the gap between flashy showpieces and the unglamorous backend systems that actually save time—triggered a core memory for me.

Back in 1991, I was working for an industrial pump company. The mechanics out in the workshop needed a way to quickly order parts and track tools without fighting complex, text-heavy computer software. To solve it, I built them a visual database behind the scenes.

Instead of typing codes, the mechanics could click an icon of a nut and bolt to bring up the exact parts list for a specific pump. Click an icon of a spanner, and it took them straight to the tool allocations. It was simple, intuitive, and kept the workshop floor moving.

I also knew human nature. I added a bright red button on the screen with bold text that read: PLEASE DO NOT TOUCH! Predictably, curiosity won, and people clicked it. When they did, the computer speaker blared a loud warning siren. It scared the living daylights out of them every single time!

It gave the workshop a great laugh, but more importantly, the mechanics loved the system because it wasn't built to look clever. It was built to eliminate friction for the people actually doing the work.

Reflecting on Igor's post, I realised my approach to technology hasn't changed in over thirty years. Building backend automation with AI today isn't about staging flashy demos or engaging in "AI theatre." It is about doing what I was doing in 1991—building quiet, practical backend systems that handle the heavy lifting behind the scenes.

The software has evolved, but the principle remains identical: build systems that remove friction and protect the energy required for actual execution. 🔢👩🏻‍💻🔩🔧🟥

24 comments

The 1991 Workshop Siren: Why Practical Architecture Always Beats "AI Theatre".