I wholehearted believe that the most saved people on this planet – the ones who have gone through the most suffering and temptations and endured the darkest situations – are without a doubt, computer guys.
In my mind, this is a fact.
I arrive at a client’s place at 4 pm to install a network printer, an absolute necessity for their business; even worse, their existing printer is on its last legs and doing weird things. I’ve installed printers hundreds of times and so I plan to knock this place over in an hour, from start to finish, and leave a hero.
Unbox the printer, set it up, connect it to the network and set something called a static ip. The static IP is like an unchangeable house address – needed because all the printers print to this address, and if it changes problems ensue. Estimated time to set the static IP: 3 minutes. Set all the PCs to print to the printer: ten minutes each max, times six PCs, so we’re talking an hour, leaving time to shoot the breeze with the boys.
I set the static IP. Of course, we have to check to make sure it works, and at a PC I ping the printer. This means, I issue a command that says, “Hey, printer, are you out there on the network at this IP address?” If all is well, the printer responds, “Heck, yes I am, how are you?” Can we all then say: “Life is good.”
Printer is pinged, but does not respond. It is not found on the network.
Where is the printer?
The printer is beside me but apparently not on the network. Well, it’s time to check all the obvious possible issues. Is the stupid cable securely plugged into the printer? Did I type the right IP address? Things like that.
I do all the above and all looks good. Let’s try pinging again. I do. No printer.
At this point, we embark on a huge, worse-case scenario that boils down to: why can’t I see the stupid printer on the network, and what could possibly be wrong? To make life even better, the owners son (who has great sway) is watching my every step, every keystroke entered and is wondering what is wrong and asks, “Can I print now?”
“No, you can’t print now,” I say and I continue with my troubleshooting.
“What could be wrong?”
I start to explain, that the static IP address for some reason is not being recognized by other devices on the network and quickly lose him. It’s like when my mechanic tries to explain what happened when my car’s front end keeps shaking, and how this is attached to that and how this wears down and effects that, and in the end you have a shaky front end but it can all be fixed for $300, as long as this other thing isn’t worn at all.
“Oh,” he says. “Could it have something to do with the computer beside it? We could never get that to print to the old printer.”
“No, it’s not the PC beside it!” I say. By this point I have lost my spot in my troubleshooting sequence and try to find my way back to what I was trying to determine, when fortunately he leaves the room.
We try this and that and there are different ways to setup a printer – some very much less ideal than simply having all the PCs print over the network directly to it – and every way we try leads to failure. An hour and a half has passed and all the employees have left, so it’s just me and the owners son in the building now, and I find him and ask, “Is it ok that I stay? Do you have time?”
“Yeah, that’s fine,” he says. “I’ll just be here watching basketball.”
Here is a PC in the back office, where he can lean back like a big boss with his feet up and watch some game, and luckily he is in one room and I am in the other. That helps.
But not much, because everything I do is fraught with failure. Two hours have passed, and we’re not much farther than we were when I hit the door. There is a time to valiantly fight, and there is a time to valiantly give up, and I choose the latter.
“I’m going home,” I tell the owners son, still watching a game.
“It didn’t work out?” he asks.
“No,” I say, admitting defeat. There is success as a computer guy, where the balloons fall and someone cuts the cake, and there is abject defeat, where the question is, “Does this guy know what he is doing?” I am in the latter category with this job. But I must explain: it could be much, much worse. Being responsible for losing 15 years of data because you didn’t properly setup the backup system – that is much much worse. That is grounds to shoot dust in your face, swear at you with many bad words, get the pitchforks out and run you out of town.
So it could be worse.
I take the printer home and mess with it, when my mind is clear. I find a way to put it on my home network but I have to say: this printer is weird, and I’ve never had to do what I did to get it to work the way it should. It’s like that in a computer guy’s life. When it should work, it doesn’t for reasons inexplicable, and when it shouldn’t work, it suddenly does. A simple job can end up taking hours, and a complex job can be surprisingly quick. No one knows what lurks in the day of a computer guy. It can be anything.
That’s why we computer guys have been tried and tested more than other mere mortals. We have fought bigger lions and scaled higher mountains, and we have Kryptonite somehow embedded in our DNA that allows us to handle insurmountable situations – situations that involve what mere mortals can only hope to comprehend and fix, that is: issues with computers.
Will anyone disagree?