There's an old saying I had taped to the side of my monitor when I was doing IT consulting: "A lack of preparation on your part does not constitute an emergency on my part." I can't tell you how many times I wished that sign could talk for me.

Software first. I'd tell a client for months that their Access database needed an overhaul. Too many nested macros, fields jammed into one table, and queries slower than a shuttlecraft at low impulse. I'd explain that one day, this Frankenstein monster was going to fall apart. But no, they were "too busy" to schedule the work. And then, inevitably, the day comes when it fails right before payroll is due, and suddenly my phone is blowing up. Now it's an emergency. But no, it's not my emergency. It's the entirely predictable result of ignoring maintenance. Sure, I can make it there by 2pm. But now you're paying my "emergency" rate.

Same with hardware. I used to warn clients that servers need TLC too. Dust isn't just ugly, it's conductive. Fans clog up, drives fail, power supplies cook themselves. I'd say, "Let me come in, back it up, blow it out, keep it healthy." In fact, I had a regular preventative maintenance plan I called "PC Doctor" where I took care of all the essentials, and I recommended it semi-annually (1). But they'd put it off, and then one day - boom - down goes the only domain controller in the building. The frantic call would come in: "We need you here NOW." My polite-but-firm answer? "I'll get there when I can, but I told you this was coming."

This isn't just tech. Look at politics. Every few months we go through another "government shutdown" panic. They know the budget deadline is coming. Everyone knows it. Yet somehow, it becomes a last-minute cliffhanger, like a bad TV series that never learns how to pace itself. Suddenly, people scramble as if it's a surprise. But it isn't. I swear these guys are just doing it for the theatrics.

Same in personal life. We've all had that friend or family member who refuses to plan, then dumps a crisis in our lap. "I forgot to buy the cake for the party - can you bake one real quick?" No, I can't. You knew about the party just as long as I did. Poor planning does not equal my emergency. Best I can do is stop at Publix on the way there.

Health is no different. People cruise through life eating garbage, never exercising, never thinking about tomorrow. Then they hit 55, the doctor says "angioplasty," and they're shocked, and they wonder how they got to that point. But the body doesn't usually just collapse overnight. It's years of deferred maintenance. My own grandfather died at 55 from a heart attack. Italian. Crap diet. Never exercised. Sure loved his pasta though.

Cars are another classic example. How many of us have waited just a little too long for that oil change, simply because it was inconvenient? I'll admit it: when I was 17, I drove my first car straight into the ground because no one had ever explained to me what an oil change was or why it mattered. Engines don't seize up out of nowhere - they beg for attention mile after mile until one day they stop begging and just die. That's not bad luck, that's deferred maintenance cashing in its chips. Then again, it was a Renault, maybe it was just fulfilling its destiny. LOL. JK.

And of course, Star Trek illustrates this perfectly. The Ferengi were notorious for cutting corners on maintenance - not necessarily for lack of planning (they were brilliant planners) but more for saving latinum. Quark would run his holosuites until they were sparking, then scream for Chief O'Brien to fix them immediately. That's not an emergency - it's negligence catching up with you. If you don't keep up with maintenance, don't expect someone else to beam in and save you at warp speed.

The moral of the story is simple. Emergencies are often just procrastination in disguise. If you don't make time for maintenance, backups, or planning, you'll make time for failure. And when the failure happens, don't expect everyone else to leap into action to save you. Your lack of preparation isn't my emergency.

And when it comes to your Access database: backup, Backup, BACKUP AGAIN!

LLAP
RR

(1) Semi-annually means twice a year. Bi-annually means every two years. I will die on this hill.