The Day Payroll Almost Didn’t Happen
“Are we getting paid today?”
Originally Published on my JorgeDiaries Substack here
In my early 20s, I worked for a company that delivered “timeshare computing.” This was long before Software as a Service (SaaS) was a buzzword. We installed physical terminals at client sites and connected them back to our servers via modems. It was scrappy, fragile, and—when things went wrong—uncomfortably real.
One Friday morning, the call came in before I’d even finished my first coffee.
Payroll wasn’t just slow or buggy. It was completely down. And in the world of blue-collar labor, “Monday” isn’t an answer. People were expecting their checks that morning.
I grabbed a terminal, threw it in my car, and raced 45 minutes down to Boca Raton.
The Pressure Cooker
The client was a steel distributor. When I pulled into the lot, I felt the weight of the situation immediately. A group of men were leaning against the trailer, arms crossed, biceps flexed, eyes locked on me as I walked toward the door with my equipment.
It was half curiosity, half silent pressure. Inside, the atmosphere wasn’t much better. The owner and his wife were on edge, hovering as I began the diagnostic “triage.”
- Hardware? Fine.
- Printer? Operational.
- Modem? Connected.
That narrowed it down to the two not so good scenarios: Application failure or Data corruption.
Back then, restoring an application or database wasn’t a one-click operation. It meant a frantic coordination with our main office, rebuilding configurations by hand, and praying that the backup tapes held.
The Human Element
As the restore process ticked away, the trailer got hotter. Not just from the Florida sun, but from the constant stream of people “popping in” with minor questions—checking to see if the kid in the tech shirt had saved the day yet.
They weren’t worried about the software. They were worried about rent, groceries, and their families.
At one point, the owner pulled me aside. “Do I need to go to the bank?” he whispered. “Should I start withdrawing cash just in case?”
I told him I didn’t think it would come to that, but I suggested it wasn’t a bad backup plan. That’s the moment the gravity really hit me. This wasn’t a “system issue.” This was a livelihood issue.
The Sound of Success
About three hours in, we were ready. We ran the tests. The data held. The manager re-entered the batch, her fingers flying across the keys.
Then came the sound I’ll never forget: The rhythmic, mechanical chug of the impact printer.
Checks began to slide out, one after another. The tension in the room evaporated instantly. By 1 PM, payroll was done. I was 24 years old, sweating through my shirt, and running on pure adrenaline.
The Lesson
That day taught me two things that have stayed with me for decades:
- Pressure reveals capability. You don’t know how well you know your craft until the room is hot and the stakes are high.
- Technology is never abstract. When a system fails, the impact isn’t technical—it’s human.
We’ve moved from single payroll systems to a world where technology is woven into every second of our lives. Our phones, our banking, our sense of connection—it’s all part of the same digital fabric. When it works, it’s invisible. When it breaks, it’s disorienting.
That afternoon in Boca Raton gave me a lasting perspective: Behind every line of code and every server rack is a chain of real-world consequences.
As we build and support the next generation of tech, we owe it to the people on the other side of the screen to remember that responsibility. Because at the end of the day, it’s not about the “uptime”—it’s about the people waiting for their checks.
Like these stories? Want more? Like it, comment and share it! —
Subscribe to my JorgeDiaries emails for other personal stories like this