The hum of the HVAC system in the conference room is exactly 52 decibels, a frequency that vibrates directly against the back of my molars. On the screen, a slide deck glowers with the confidence of a predator. Marcus, the Vice President of Infrastructure, is gesturing toward a green circle that represents ‘Seamless Global Access.’ He uses the word ‘frictionless’ 12 times in 62 seconds. I am sitting in the corner, nursing a lukewarm coffee, watching the chat window on my laptop. It is a private channel, away from the prying eyes of the governance committee.

‘He’s doing it again,’ Sarah types. ‘The licensing server hasn’t checked in for 32 hours. If the cache clears, the entire Northeast region goes dark.’

Marcus is currently explaining how the transition to the new environment has been ‘extraordinarily smooth.’ It is a beautiful performance. He has the kind of posture that only comes from never having to manually edit a registry key at 3:02 AM. He speaks in verbs that have no physical weight: leveraging, optimizing, synergizing. To him, the infrastructure is a conceptual drawing, a series of pipes that always flow in the right direction because that is how they were drawn on the whiteboard. He cannot define the difference between a user-based and a device-based permission set, yet he is the one signing the declaration of success.

I think about Isla M.-L. She is an ice cream flavor developer I met at a trade show 22 months ago. Isla doesn’t deal in ‘frictionless’ concepts. If she wants to create a ‘Salted Irony’ flavor using charcoal and burnt caramel, she has to understand the specific molecular weight of the stabilizers. If the fat content is off by 2 percent, the texture turns into something resembling wet cardboard. She told me once that the hardest part of her job isn’t the tasting; it’s the industrial freezers. She spent 82 days trying to calibrate a batch freezer that refused to hold a consistent temperature. Her boss kept asking for ‘innovation,’ but Isla was just trying to keep the liquid from crystallizing.

We are currently in the ‘crystallization’ phase of this project, but Marcus is describing a milkshake.

I recently turned the primary authentication server off and on again. It’s the ultimate admission of defeat, isn’t it? It is the technical equivalent of hitting a television set to make the picture stop flickering. We do it because we have built systems so complex that we no longer truly understand why they stop working; we only know how to reset their state to a point where they were previously working. It’s a ritual. We are like ancient priests throwing salt over our shoulders, hoping the gods of the kernel will be appeased for another 72 hours.

In most organizations, reporting ‘red’ on a dashboard is seen as a failure of character. It implies that the person in charge of that metric is incompetent. Consequently, everyone finds a way to make the dashboard ‘watermelon’ style: green on the outside, deep bloody red on the inside. We optimize for the appearance of progress. We tell the leadership that the ‘scalable seamless access’ is live, while the engineers are behind the curtain holding the wires together with metaphorical duct tape.

Take the deployment of remote desktop environments, for instance. To an executive, it’s a line item. You buy the hardware, you get the software, you grant access. But for the person in the trenches, it’s a nightmare of dependencies. You are dealing with legacy applications that haven’t been updated since 2012, user profiles that are 42 gigabytes large for no reason, and the constant, thrumming anxiety of licensing compliance. When you’re staring at the licensing server, trying to figure out why the windows server 2022 rds user cal isn’t propagating to the session host, you aren’t thinking about ‘strategic synergy.’ You are thinking about whether you can quit your job and become an ice cream developer like Isla.

I have made mistakes. I once deleted a production database because I had 22 tabs open and thought I was in the staging environment. I admitted it immediately. The fallout was 102 minutes of downtime and a permanent twitch in my left eyelid. But the trust that came from that vulnerability was more valuable than any ‘green’ status report I’ve ever filed. My team knew that when I said things were working, I meant it, because they had seen me admit when they weren’t. Marcus, however, has never admitted to a mistake in the 422 days he has been with the firm. To him, errors are just ‘learning opportunities’ that happened to someone else.

There is a specific kind of loneliness in being the person who knows how the machine actually works. You see the cracks in the foundation while everyone else is admiring the wallpaper. You know that the ‘seamless’ experience is actually a series of 12 different scripts running in a specific order that only works if the moon is in the right phase. You realize that the $272,000 spent on the new ‘security layer’ is actually just a glorified firewall rule that Dave wrote in 22 minutes because the vendor’s software didn’t actually work as advertised.

Isla called me last week. She’s quitting the ice cream business. She said she’s tired of the ‘theatre of the artisan.’ Apparently, the company wanted her to pretend that every batch was hand-churned by monks in the Alps, even though it was all coming out of a factory in New Jersey. She couldn’t reconcile the story with the chemical reality. I envied her. In tech, we are expected to live in that reconciliation forever. We are expected to be the monks and the factory workers at the same time, while Marcus tells the world that the ice cream is being delivered by angels.

We need to stop rewarding the performance of control. We need to start rewarding the honesty of the struggle. The most resilient systems aren’t the ones that never fail; they are the ones where the failure is visible, understood, and managed. A ‘green’ dashboard is a lie. A ‘yellow’ dashboard is an honest conversation. But in a world where the Vice President needs ‘strategic certainty’ to justify his existence, honesty is a dangerous career move.

I look back at the screen. Marcus is finishing his presentation. The final slide is a picture of a mountain climber at the summit. The text says ‘Victory through Visibility.’ Dave sends a message in the chat: ‘The licensing server just hit 100% CPU usage. Here we go again.’

‘The licensing server just hit 100% CPU usage. Here we go again.’

I close my laptop. I can feel the ‘Salted Irony’ in the back of my throat. I wonder if I can find a way to turn the entire company off and on again. Maybe then, the textures would finally align, and we could see the infrastructure for what it actually is: a fragile, beautiful, human-made mess that requires more than just a green circle to stay upright.

I stand up and walk toward the door. Marcus catches my eye and gives me a thumbs-up. I give him one back. It’s the least I can do. After all, we are both part of the same performance. The only difference is that I know when the curtain is going to fall, and he thinks the play lasts forever. I wonder if Isla M.-L. ever found a freezer that actually worked, or if she just learned to love the ice crystals. I think I know the answer. You don’t fix the crystals; you just learn how to sell them as ‘crunchy texture.’ 12 minutes later, I’m back at my desk, opening the console, ready to reset the state once more.