The Brioche Bun and the Wood Glue

Marcus J.-M. is currently using a pair of surgical tweezers to place exactly 107 sesame seeds onto a brioche bun that has been meticulously coated in industrial-strength wood glue. He is a food stylist, a man whose entire professional existence is dedicated to the gap between what things look like and what they actually are. I’m sitting on a crate in the corner of the studio, watching him work, when my phone buzzes. It’s Sarah from Marketing. She doesn’t say hello. She doesn’t ask if I’ve eaten. She just says, ‘Hey, we need to add a small checkbox to the user profile page. Just a little thing to track if they prefer oat milk or almond milk for the newsletter perks. It’s just one more field, right?’

I look at Marcus. He’s currently painting a raw steak with brown shoe polish to make it look ‘seared.’ I feel a kinship with him. Sarah thinks the website is like a Word document. She thinks you just hit ‘Enter,’ type a new line, and the universe adjusts. She doesn’t see the 7 interconnected APIs that are currently holding our user data together like a game of high-stakes Jenga. She doesn’t see the legacy authentication system-a piece of software written in 2007 by a guy who now lives in a yurt-that will inevitably break if we introduce a new schema element without a full regression test. To her, it’s a checkbox. To me, it’s a six-month project involving 47 separate touchpoints in the codebase and a potential database migration that could take the entire site offline for 17 hours.

The Great Abstraction

This is the Great Abstraction. As our tools become more polished, the people using them become more convinced that the underlying reality is equally smooth. They see a button; they don’t see the 237 lines of logic that validate the user’s session, check their permissions, ping the payment gateway, and update the inventory. We have built such beautiful interfaces that we’ve convinced the world that complexity no longer exists. It’s a dangerous lie. It’s the same lie that led me to a department store yesterday, trying to return a high-end blender without a receipt. I knew I bought it there. They knew I bought it there. But the ‘system’ required a specific 17-digit transaction code that only exists in a physical slip of thermal paper that is currently decomposing in a landfill. The clerk looked at me with a mixture of pity and robotic indifference. The system is rigid. It is not a Word document. You cannot just ‘add a field’ to a return policy when the database architecture doesn’t allow for a ‘Lost Receipt’ exception.

I spent 47 minutes arguing with a manager named Gary, who kept saying, ‘I’d love to help you, but the field is greyed out.’ That’s the reality of our digital world. We are living inside greyed-out fields.

When Sarah asks for her oat milk checkbox, she’s asking me to go into the foundational concrete of our building and move a load-bearing pillar six inches to the left. She thinks she’s just asking me to hang a picture frame.

The Wizard and the Components

Marcus J.-M. stops tweezers-in-mid-air. He looks at the burger, then at me. ‘You know,’ he says, his voice muffled by a silk face mask, ‘people think this burger is edible. If they bit into it, they’d break their teeth on the toothpicks I’ve used to keep the lettuce from sagging. It looks perfect, but it’s a structural nightmare.’ I tell him about the checkbox. He laughs, a dry, cynical sound that reminds me of a hard drive failing. He gets it. In his world, if you want the cheese to look melty, you hit it with a blowtorch for exactly 7 seconds. If you do it for 8, the whole thing collapses. In my world, if you add a field to the user table without updating the caching layer, the site latency spikes by 37 percent and the mobile app starts crashing for 777 users in the Midwest.

We have reached a point where the users of technology are effectively wizards who have forgotten that magic requires components. They want the fireball, but they don’t want to provide the bat guano and sulfur. They want the ‘simple’ change, but they don’t want to hear about the RDS CAL or the server licensing costs that escalate when you start scaling your remote access to accommodate 107 new remote contractors who all need to see that oat milk data in real-time. Everything is connected. Nothing is ‘just’ a field.

The Logic Trap

I think back to the blender. The reason I couldn’t return it wasn’t because Gary was mean. It was because the database designers in 2017 decided that the ‘TransactionID’ was a non-nullable primary key linked to the ‘StoreInventory’ table. To create a return without that ID would require a ghost transaction that would throw off the end-of-month audit for the entire regional district. It’s a logic trap. And now, I’m being asked to build a new one.

Every ‘just’ hides a mountain of technical debt. We’ve spent the last 27 years abstracting away the ‘how’ so that people can focus on the ‘what,’ but in doing so, we’ve created a class of decision-makers who are functionally illiterate regarding the systems they manage. They see the brioche bun; they don’t see the wood glue.

“

I’m trying to keep the lettuce from sagging. I’m trying to make sure the steak doesn’t taste like shoe polish when a real user finally tries to take a bite.

I start typing a response to Sarah. I mention the 47 API endpoints. I mention the fact that our current database schema is so tightly packed that adding a single column will require a 7-hour maintenance window. I mention the security audit. I’m being honest, but I know how I sound. I sound like a gatekeeper. I sound like Gary at the department store, telling her that the field is greyed out. But I’m not trying to be difficult. I’m trying to keep the lettuce from sagging. I’m trying to make sure the steak doesn’t taste like shoe polish when a real user finally tries to take a bite.

Living in the Basement

There is a specific kind of exhaustion that comes from explaining the law of thermodynamics to someone who just wants to buy a perpetual motion machine. I see it in the eyes of every sysadmin I know. It’s the look of someone who knows that if they say ‘yes’ now, they will be the ones awake at 3:07 AM on a Tuesday when the ‘oat milk’ field causes a buffer overflow in the legacy mailing list script. We are the ones who live in the basements of these abstractions. We are the ones who know exactly how much wood glue it takes to make a website look like it’s functioning perfectly.

The Honest Lie

Marcus finally finishes the burger. It looks glorious. It looks like the best thing you’ve ever seen. It is a lie. He picks up a spray bottle of glycerin and gives the lettuce a light misting. ‘Now it looks fresh,’ he says. I look at my phone. Sarah has replied. ‘Also, can we make the checkbox blue? Just a quick CSS change.’ I put my phone face down on the crate. I think about my blender, sitting in its box in the trunk of my car, a useless piece of high-end engineering that cannot be returned because of a missing string of 17 digits. The world is a series of interlocking, uncompromising systems, and we are all just trying to find a way to navigate them without breaking our teeth on the toothpicks. I decide I won’t reply for at least 47 minutes. I need to watch Marcus paint some fake condensation onto a soda can first. It’s the only thing that makes sense today-an honest lie in a world of ‘simple’ requests that are anything but.