I am staring at a stack of fifty-nine Dell Latitudes, and my hands are actually shaking. It is on a Tuesday, or maybe it’s Wednesday; the distinction stopped mattering when the office lights went into energy-saving mode and left me in a pool of flickering amber.
The air in the staging room smells like fresh plastic, ozone, and the kind of desperation that only happens when you realize your entire infrastructure was built on the assumption that people would occasionally come into the office to touch the network.
They aren’t coming back. Not tomorrow, not next month. And forty-nine of these machines are refusing to join the domain because I forgot that our local DNS server doesn’t like the way the new VPN tunnel handles the suffix. It’s a small thing. A tiny, insignificant bolt.
The Vibration of Screaming Metal
June J.D. would have seen it coming. June is a carnival ride inspector I met years ago at a diner in Ohio. She has a neon vest with 19 pockets and carries a 19-millimeter wrench that she uses to tap at the steel frame of the Tilt-A-Whirl.
“She told me once that you can hear a bad bearing before you can see it. ‘It’s the vibration,’ she said, leaning over a plate of cold fries. ‘Everything in this world is just vibrating, and when the rhythm changes, that’s when the metal starts to scream. You just have to be quiet enough to hear it.'”
– June J.D., Carnival Inspector
I wasn’t quiet. I was loud. I was busy. I was “scaling.” I was doing everything except listening to the vibration of our licensing servers.
Sarah’s Digital Tombstone
The school district IT director I worked with back then, a woman named Sarah, still has a spreadsheet on her desktop. It’s called MASTER_DEPLOY_FINAL_v9.xlsx. It contains exactly 319 rows of data.
Each row represents a laptop, a student, and a manual activation code because the management system we spent $19,999 on simply folded under the pressure. It couldn’t handle the heartbeat of 319 devices hitting the gateway from residential IP addresses all at once.
The record of the where Sarah didn’t see her kids because she was manually typing “Genuine” into the void.
Sarah refuses to delete that file. She hasn’t opened it since , but it sits there like a digital tombstone.
The Words Without Jagged Edges
We don’t talk about this. In the industry, we talk about the “Digital Transformation” and the “Cloud Pivot.” We use these smooth, rounded words that don’t have any of the jagged edges of the actual experience.
We don’t talk about the night the KMS host died and 239 teachers woke up to a black desktop and a watermark telling them they were using pirated software. We don’t talk about the shame of being the “expert” who didn’t realize that the VPN wouldn’t pass the activation packets without a specific GPO tweak that we hadn’t touched since .
I felt like I was in that moment where you wave back at someone who is actually waving at the person behind them-a frantic, misplaced enthusiasm that ends in a sudden, cold realization of invisibility. I was waving at the server’s heartbeat monitor, thinking we were connected, but the server was talking to a gateway that didn’t exist anymore. I was redundant. My plans were redundant.
Institutional Memory is Vapor
The pandemic was the largest live IT exercise in modern history, and yet, almost none of the real lessons have been written down. We documented the “how-to” for the users, sure. We wrote 19-page PDFs on how to mute yourself on Zoom.
But we didn’t write down how we broke the back of the Active Directory to make it work. We didn’t record the 49 different ways the firewall rules were bypassed just to get the accounting department back online.
Institutional memory is a fragile thing. In technology, it’s practically vapor. We replace our tools every few years, and we assume the knowledge is built into the tool. It isn’t. The knowledge is in the scar tissue of the people who stayed up until trying to figure out why the activation grace period wasn’t resetting over the tunnel.
I spent one Saturday just trying to understand the relationship between our internal licensing and the public-facing IP of the VPN concentrator. I realized then that our documentation was a lie.
It described a “perfect” system, a system where everything was local, everything was wired, and everyone was honest. It didn’t describe the jagged reality of a home Wi-Fi network that is competing with a microwave and a baby monitor.
In those moments, you find yourself looking for resources that aren’t marketing fluff. You look for the documentation that actually understands the struggle of the small-shop admin. This is where sites like
come into the conversation-not as a corporate solution, but as a technical touchstone for those trying to understand the mechanics of activation in a world that moved faster than the official manuals could keep up with.
You start to realize that the “official” way was designed for a world that ceased to exist on a Friday in March.
The Zipper in the Parking Lot
June J.D. would look at my server rack and she wouldn’t see the LEDs. She would see the stress fractures. She’d tell me that by year , we’ll have a whole generation of infrastructure built on top of the “temporary” fixes we put in place during the lockdown.
We’re building skyscrapers on top of a carnival ride that was only meant to run for a weekend.
I once pushed a script to 49 machines that accidentally renamed them all to “DESKTOP-TEMP.” I was tired. I was waving at the person behind me again. I spent the next undoing the damage, machine by machine, over a remote desktop connection that kept dropping every .
That’s the stuff that doesn’t make it into the quarterly report. The report says “Remote workforce successfully enabled.” It doesn’t say “Admin nearly had a breakdown over a misplaced semicolon.”
The Quarterly Report
“Remote workforce successfully enabled through robust VPN architecture.”
The Server Room Reality
“Held together by Sarah’s 319-row spreadsheet and a few desperate Google searches.”
Why don’t we write this down? Because to write it down is to admit how close we came to total failure. It’s to admit that the “robust” systems we sold to the board were actually being held together by Sarah’s 319-row spreadsheet and a few desperate Google searches.
We want to believe we are architects, but during the lockdown, we were just carnival ride inspectors trying to keep the Zipper from throwing a car into the parking lot.
The drift is already happening. We’ve replaced the laptops. We’ve upgraded the VPN. The admins who remember the specific, hot smell of the server room during that first week are moving on. They are retiring, or they are becoming managers who “consider” (god, I hate that word) the high-level strategy without ever touching a command prompt.
When the Next Vibration Starts
And when the next vibration starts-when the rhythm of the metal changes again-the new guys won’t know where to look for the stress fractures.
They won’t know that the licensing server has a specific quirk when it hits of uptime. They won’t know that the DHCP scope was once expanded so fast that it started overlapping with the static IPs of the printers. They’ll just see a red light and wonder why the documentation says everything is fine.
Documentation is about admitting that you bypassed the main relay with a piece of copper wire and a prayer. It’s about admitting that the system is imperfect.
I think about that spreadsheet a lot. 319 rows. It’s a small number in the world of Big Data, but it’s a massive number when you’re the one who has to verify every single one. Sarah keeps it because it’s her medal of honor. It’s her proof that when the world stopped, she kept it spinning, one manual license key at a time.
We owe it to the version of ourselves that didn’t sleep to be more honest about the “hacks.” We need to stop pretending that the deployment was seamless. It was a war. It was a messy, loud, confusing struggle against a set of assumptions that were proven wrong in a single weekend.
If we don’t write down the failures, the next generation will inherit a system they don’t understand, waiting for a crisis they aren’t prepared for. They’ll be looking for the bolts, but they won’t have a June J.D. to tell them where the metal is screaming.
Is the documentation you’re writing today meant to help someone succeed, or is it just meant to cover the fact that you’re still not sure why it’s working?
I looked at the Latitudes again. 59 of them. They were finally all activated. The watermark was gone. The users were happy.
I shut down my terminal and walked out into the cool, pre-dawn air. I saw a guy jogging past, and he waved. I started to wave back, then stopped.
He was waving at his friend behind me. This time, I just kept walking. I knew exactly where I was.