Nearing the final sliver of that digital thermometer, the progress bar remains frozen at ninety-nine percent while the fan of my laptop screams like a jet engine trying to take off from a kitchen table. It has been sitting there for 23 minutes. My entire Saturday afternoon, a rare 3-hour window of quietude before the chaos of the household resumes, is being swallowed by a mandatory security patch that I didn’t ask for and certainly didn’t want. This is the modern ritual: the sacrifice of human time at the altar of the perpetual update. We no longer own tools; we rent permissions to use shifting sets of code that are never quite finished. I can feel the heat radiating from the chassis, a physical manifestation of a thousand lines of unoptimized instructions fighting for dominance over my hardware. It is a slow, agonizing theft of agency.

I spent nearly 63 minutes earlier today writing a scathing critique of the latest UI overhaul in my primary work suite, only to delete the entire thing in a fit of pique. It felt too polished, too much like the very thing I was complaining about. The irony of polished complaining about unpolished software wasn’t lost on me. Instead, I’m looking at this progress bar and thinking about Michael B.K., a man I met last year while he was restoring the facade of a bank built in 1903. Michael is a mason, the kind who understands that the soul of a structure is in the mortar, not just the stone. He spent 13 days matching the specific shade of a century-old brick. When he finishes a wall, it is done. It does not require a weekly check-in to ensure the bricks haven’t suddenly decided to rearrange themselves for a better ‘user experience.’ There is a permanence in his work that makes our digital landscape look like a fever dream of shifting sand.

The Illusion of Progress

Michael B.K. once told me, while wiping a smear of grey dust from his forehead, that the problem with modern construction-and by extension, modern life-is the loss of the ‘finished’ state. We were standing in front of a 43-foot archway. He pointed to the keystone and said if that piece wasn’t right the first time, the whole thing would eventually become a pile of 503 separate problems. Software engineers, however, have been taught that the keystone is optional in the first version. They’ll just ship the archway with a temporary wooden brace and promise to send a better stone via the cloud in 3 weeks. But the cloud is heavy, and the brace is starting to creak under the weight of our expectations.

We have become unpaid beta testers in a grand experiment of continuous deployment. The tech industry has effectively shifted the burden of quality assurance from their air-conditioned labs to our living rooms. If a piece of software crashes on my machine, I’m the one who loses the 33 minutes of unsaved work. The company just gets another data point in their telemetry dashboard. They see a 0.3 percent failure rate; I see a ruined afternoon. It’s a cynical trade-off where ‘agile’ has become a synonym for ‘incomplete.’ We are told this is progress, that the ability to fix bugs on the fly is a feature, not a failure of the initial design. But when was the last time an update actually made your life simpler? Usually, it just moves the button you use 23 times a day to a sub-menu that requires 3 extra clicks to find.

The Relinquishing of Control

I remember when software came in a box. You bought a version, you installed it, and it stayed that way until you decided to buy a new box. There was a contract of stability. Now, that contract has been shredded and replaced with a ‘Service Agreement’ that basically says, ‘We can change anything at any time, and if it breaks, that’s just the price of being connected.’ The anxiety of the update is real. Every time I see that little red notification dot, I feel a spike of cortisol. Is this the update that breaks my printer drivers? Is this the one that makes my favorite shortcut obsolete? We are living in a state of 103 concurrent anxieties, all mediated by pixels that refuse to stay still.

“

The burden of quality is the only thing we can’t outsource to the user.

There is a fundamental dishonesty in the way we talk about ‘living’ software. It’s not alive; it’s just unfinished. Imagine if your car manufacturer showed up at your house at 3 in the morning to change the shape of your steering wheel. You’d call the police. Yet, we allow software companies to do this daily. They call it ‘evolution,’ but it feels more like a slow-motion home invasion. We’ve lost the right to a static environment. I’ve seen 43 different versions of a single spreadsheet app in the last year, and none of them have fixed the basic formatting bug that has haunted me since version 3. Instead, they added 23 new emojis and a sidebar that suggests ‘collaborative workflows’ I will never use.

This culture of the perpetual update is a direct result of the ‘Move Fast and Break Things’ ethos that has poisoned the well of engineering. It’s an ideology that prizes speed over durability. Michael B.K. wouldn’t last a week in a modern software sprint. He’d be fired for spent 3 days ensuring the foundation was level. ‘We need to ship the foundation now,’ the project manager would say. ‘We can level it with a software patch later.’ But you can’t level a physical building with a patch, and as our digital lives become more integrated with our physical ones, the lack of a level foundation is starting to show. We are building digital cathedrals on top of quicksand.

The Value of Stability

In a landscape where ‘breaking things fast’ has become a religion, finding an outlier like ems89 feels like finding a mason who actually cares about the plumb line. It is a reminder that stability is not a lack of progress; it is the prerequisite for it. If I am constantly worrying about the ground shifting beneath my feet, I can never focus on building anything of value. True innovation isn’t about how many updates you can push in a 23-hour cycle; it’s about how much trust you can build with the person on the other side of the screen. Reliability is the ultimate luxury in a world of planned obsolescence.

I’m looking at the clock. It’s been 53 minutes now. The progress bar has moved to 99.1%. It’s a cruel joke, a decimal point of despair. I find myself wondering if the engineers who wrote this code ever feel the weight of the millions of hours they are collectively stealing from humanity. If you multiply this 53-minute wait by 3 million users, you get a staggering amount of lost human potential. We could have built 333 cathedrals with that time. We could have learned new languages, or sat on a porch and watched the sunset, or finally figured out how to bake a decent loaf of sourdough. Instead, we are staring at blue bars.

The Exhausting Race

There’s a specific kind of silence that happens when you’re waiting for tech to catch up with your intent. It’s a hollow, expectant silence. It’s the sound of a 1003-dollar machine doing absolutely nothing of value. I think about the 63 pages of documentation I once read for a server setup that changed completely 3 days after I finished it. The knowledge was rendered obsolete before I could even apply it. This is the ‘Red Queen’s Race’ of the digital age: we have to run twice as fast just to stay in the same place. It is exhausting, and it is entirely unnecessary.

Demand the ‘Finished’ State

Maybe the answer is to stop clicking ‘Update’ until it’s absolutely necessary. To treat our digital tools with the same skepticism we’d treat a contractor who wants to renovate our kitchen every Wednesday. We need to demand a return to the ‘Finished’ state. We need to value the Michael B.K.s of the digital world-the people who realize that a tool should be a silent partner, not a demanding toddler. A tool that is always changing is not a tool; it’s a distraction.

As the progress bar finally clicks over and the screen flashes black to reboot, I realize I’ve lost the window of time I had to actually work. The sun has shifted 23 degrees across the floor. The house is waking up. The quiet is gone. I am ‘updated,’ but I am also defeated. My software is now slightly more secure against a threat I’ll never face, but I am less secure in my own productivity. I have been optimized into a corner. And tomorrow, I’m sure, there will be another 3 updates waiting for me, promising to fix the problems created by the one I just installed. Is it too much to ask for something that just works, and stays working, until the stones themselves turn to dust?