My eyes are burning. I am squinting through a chemical haze of budget-brand shampoo because I was in too much of a hurry to rinse properly this morning, and now the world is a smeared, alkaline mess. It is fitting, really. It matches the clarity of the presentation currently flickering on the wall of Conference Room 6, where a man named Greg-who has never written a line of code but recently finished a three-hundred-and-forty-six-page biography of an abrasive tech billionaire-is telling us we need to ‘break more things.’
We are living in a cargo cult. In the South Pacific after World War II, certain island tribes built life-sized replicas of airplanes out of straw and wood, hoping to summon the metal birds that used to drop supplies. They had the form, the ritual, the landing strips, but they lacked the internal combustion engine. Greg is currently building a straw airplane. He thinks that if we adopt the vocabulary of a social media startup in 2006, we will somehow inherit their valuation without having to deal with the messy reality that our ‘users’ are actually patients with chronic illnesses who really need their insurance claims to be accurate down to the last $0.06.
I shouldn’t be this angry, but the shampoo is really doing a number on my corneas. It’s hard to be diplomatic when your eyes are leaking tears of pure surfactant.
Greg’s eyes, however, are dry and wide with the zeal of the converted. ‘We’re too slow!’ he bellows, his voice bouncing off the glass walls that cost the company $56,000 last quarter. ‘I want to see 16 new features by the end of the sprint. If some of the billing modules fail, that’s just the cost of doing business. We’ll fix them in production.’
“
Greg, when a billing module fails in healthcare, a 76-year-old woman gets a letter saying her life-saving medication isn’t covered. She doesn’t ‘iterate’ on that. She has a panic attack.
– Hiroshi J., Safety Compliance Auditor
Greg waves a hand dismissively. He’s already moved on to a slide about ‘pivoting.’ It’s the classic disconnect of the modern corporate era: the confusion of speed with progress. We have forgotten that the original phrase ‘Move Fast and Break Things’ was coined by a company whose worst-case scenario was a teenager not being able to upload a photo of a sandwich. In that context, breaking things is fine. It’s a learning mechanism. In the context of 1006 patient records or the structural integrity of a heavy-duty mechanical system, ‘breaking things’ is a crime, or at least a catastrophic failure of duty.
I remember a few years ago, I tried to fix the disposal under my sink. I thought I’d ‘move fast.’ I didn’t read the manual. I broke the PVC pipe, flooded the kitchen, and ended up paying $476 for a plumber to tell me I was an idiot. I’m doing the same thing here, professionally, every time I listen to Greg. I hate that I don’t speak up more. I criticize his lack of vision in the breakroom, then I go back to my desk and try to find a way to make 16 features fit into a timeline designed for 6.
Just looking like progress
Actual sustainability
This obsession with the startup aesthetic ignores the engineering excellence that actually allowed those companies to survive. They didn’t just break things; they had world-class monitoring, automated rollbacks, and a talent density that allowed them to fix the breakages in 6 seconds. Greg doesn’t want to invest in the monitoring. He just wants the breakage because he thinks it looks like ‘hustle.’
There are places where this kind of magical thinking simply cannot exist. You see it in the trades. If you are doing Kozmo Garage Door Repair, you don’t get to ‘move fast and break things.’ A garage door spring is under enough tension to take off a person’s arm. You don’t ‘iterate’ on a spring replacement. You do it with 106% precision, or you don’t do it at all. The cargo cult of disruption hates that kind of reality because it’s boring. It requires patience. It requires acknowledging that some things are too important to be broken for the sake of a quarterly report.
I find myself thinking about the 126 pages of documentation I have to ignore to meet Greg’s new deadline. It feels like a betrayal. Not just of the company, but of the people Hiroshi is trying to protect. We’ve replaced ‘Measure twice, cut once’ with ‘Cut six times and hope you can glue the scraps together before anyone notices.’
There was a moment, around 2016, when it felt like we might move past this. There was a brief trend toward ‘slow tech’ and ‘ethical design.’ But then the market shifted, and the ghosts of the straw airplanes returned. We started chanting the mantras again. ‘Synergy.’ ‘Disruption.’ ‘Fail fast.’ I’ve used all of them. I’m a hypocrite. I sat in a meeting yesterday and told my team we needed to ‘streamline the validation process,’ which is just a fancy way of saying we should stop checking the 6 most common error codes because they take too long to verify.
My eyes are starting to feel better now. The stinging is subsiding into a dull throb. I look at Hiroshi. He’s stopped taking notes. He’s just staring at Greg with a look of profound exhaustion. It’s the look of a man who knows he’s going to be the one cleaning up the wreckage when the straw airplane inevitably fails to take flight.
The Moral Debt Is Due
We often talk about ‘technical debt’ as if it’s just an abstract concept for developers. But there’s a moral debt, too. When you move fast and break things in a field that matters, you are borrowing stability from the future. You are taking the reliability that your customers expect and spending it to buy a temporary sense of momentum. Eventually, the bill comes due. And in healthcare finance, that bill usually has 6 zeroes at the end of it.
I wonder if Greg realizes that he is the most replaceable part of this system. If he ‘breaks,’ the company just hires another guy who read the same 126-page airport bookstore manifesto. But if the data breaks, if the trust breaks, if the 16 developers on my team burn out and quit because they’re tired of being told to do bad work-that’s not something you can just fix in the next sprint.
I remember once, Hiroshi told me about a bridge that collapsed because of a single bolt that was the wrong grade of steel. It wasn’t a lack of ‘vision’ that killed people; it was a lack of attention to the boring stuff. Greg would have hated that bridge. He would have called the bolt a ‘bottleneck’ and suggested we replace it with a ‘dynamic fastening solution’ that didn’t actually exist yet.
The Cost of Neglect
Future Growth Projections
Critical Component Grade
As the meeting winds down, Greg asks if there are any questions. I want to ask him if he’s ever had to explain to a family why their insurance was canceled because of a ‘glitch’ in a feature that was rushed to market 26 days early. I want to ask him if he knows the difference between a calculated risk and a reckless gamble. Instead, I just rub my eyes, which are still red, and nod along with the rest of the room. I’ll go back to my desk and I’ll try to find a middle ground where I don’t break anything too vital, even as I’m forced to run at a pace that makes mistakes inevitable.
We are all just sitting on the runway, wearing our wooden headsets, waiting for the cargo to arrive. We’re doing the dances and lighting the fires, but the sky remains empty. The real work-the hard, slow, precise work-is being ignored in favor of the performance of progress. It’s a dangerous game to play when the ‘things’ you’re breaking have heartbeats or bank accounts.
Refusing the Hammer
There is a certain dignity in being the person who refuses to break things, even when everyone else is holding a hammer and screaming for impact. It won’t get you featured in a 206-word blurb, but at least you can look at the 6 people you care about most and know that you haven’t traded their safety for a slogan.
