February 21, 2003
Welcome to My World Pt IV

Background: A few weeks ago I receive an e-mail from Z4, stating that the president of the board of directors (the boss's boss's boss) and Z4 have decided that Z5, a member of a "special needs" volunteer advisory council, has inadequate Internet service and should be provided a gratis internet account from us. This is not an unprecedented request. I say, "fine, I can definitely do that, but..."

You see, 99% of the members of this advisory council have the computer skills of a sea sponge. Most of them literally do not know how to turn one on. I have not met this particular one, so I'm very political about it, "they'll need to have a technical person who can come out to their house to set it up for them."

Why so specific? Why so harsh? Because the last time around we provided an entire computer to a different member of this advisory council and it sat in the box for two months because they literally did not know how to get it out. I am not making this up. Getting your fingernails pulled out is only slightly less painful than having to explain over the phone which end of the power cord goes into the wall.

You see, setting up an internet connection is a real Russian roulette kind of operation. In order to work, it has to sink some hooks pretty deep into your computer. 90% of the time it goes in slick as oil on ice, but 5% of the time it blows up in some obscure way, and the other 5% of the time it takes the computer with it. You do not want to be half way across the country on the phone with Forrest "since-life-is-like-a-box-of-chocolates-lets-stick-one-in-the-floppy-drive" Gump when this happens. And for me, it always happens.

So yeah, I set the bar pretty high. They're getting an internet connection for free fer chrissakes. If they want it bad enough they'll dredge up a local techie or their IT-professional relative (ASK ME HOW I KNOW THIS) to help them out. If they don't, then they really don't need it. Yeah, I'm a bastard. You'll find out why in a second.

Fast-forward three weeks. I'm sitting at my desk, trying to figure out how to introduce a new travel system I've created for the ship when in walks Z4, the person who requested the account, trailing someone I've never seen before, who immediately starts dissassembling themself (coat, backpack, etc.) like they own the place. "Hi Scott," Z4 says, "this is ZX, they are a member of the advisory council, they wanted to talk to you." And then Z4 just walks away.

So I'm sitting here while this person makes a great, long, rambling introduction. They obviously think I should know both who they are and why they're here, but I am clueless. I gradually pick up that this is Z5. Finally out from this huge backpack comes, of all things, a laptop. "Z4 said you were going to install my new internet connection for me today." Really? How nice of him. "It was acting a little funny with the old internet connection, but I couldn't get in touch with my tech support. Hoping you could take a look at that too. Here ya go!" *thud*

Ok, some points here:

  • If a tech person touches a computer, they own it from that point on. Any little thing, any burp, wheedle, crack, or thump that happens in the next six months, no matter if it's from what he or she did to it or not, is theirs.
  • Computers are fiddly little bastards, and laptops are fiddlier still. You won't find two laptops that even turn on the same way. All sorts of fun specific software required to make one tick. Fun, specific, easy-to-blow-up, hard-to-fix software.
  • There is almost literally nothing harder in a computer tech's professional life than doing tech support over the phone. People who do help desk for a living usually only last 6 months because of this. It's like trying to teach a jumpy person Russian over the phone so they can disarm a bomb.
  • Computer person axiom #44: If the Computer is already broken, it is a Very Bad Idea to install new system software.
  • Rule of Motivating Computer People #8: Do not surprise your tech. Techs do not react well to surprises.
  • Computer person axiom #73: Working on a stranger's computer is like playing in a minefield someone else planted: full of unpleasant surprises.
  • Scott's a Bastard, Rule #3: I get paid to work on the computers of this company. It is work, it is not fun. I do not work on other people's computers unless they are a) also paying me money (LOTS of money), b) a relative, or c) giving me copious amounts of high-quality alcohol as a reward.

I say "gosh, really sorry to hear the computer is giving you trouble, but I'm afraid you'll need to get that fixed first before anything can be done for your internet connection." This is true, good advice, something I'd say to anyone. "You'll need to contact your manufacturer." Because I really don't like working on computers I've never seen before.

"But [name], the President of the Board of Directors, said you'd be able to help."

This is where I got all hard and flinty. There are two, and really only two ways to deeply piss me off about computer stuff: acting like it's the end of the world if you don't get your problem fixed right this second, and name-dropping. Especially name dropping from people who don't actually work here. "Well, I'd love to help, but unfortunately I'm not allowed to work on computers we didn't purchase." (it's not a lie, it's a deflection), "especially if it's giving you trouble. I'll be happy to provide you with what you need to get your internet connection running once the computer is fixed."

"So I'm going to have to go to my tech support anyway then?"

What, you mean the tech support you paid for when you bought the computer, tech support who's job it is to know your computer inside and out? "Yes, I'm afraid so." [SHINEY HAPPY WORKER BEE MODE] "But I'll be happy to provide you with the settings you need for a new internet account once you get it fixed."[/SHINEY HAPPY WORKER BEE MODE]

"Hmpf!" they said as they re-assembled themselves. "I guess I'll just have to go back and talk to Z4 won't I?"

After relating a similar story to a friend, they said "doesn't it just make you want to shoot yourself?"

"No," I said, "it makes me want to shoot them."

Posted by scott at February 21, 2003 04:03 PM

eMail this entry!
Comments

yeah, but could you figure out what my boxie-thingie.... y'know, the harddrive is doing wrong that I can't get the whosamadingie to go??? c'mon, it's a simple job..... it'll only take you a minute... yeah, I know I'm a couple of hundred miles away, it's not a company-owned PC and I fucked it royally already by tinkering, but it'll only take you a minute....you're smart like that!

Posted by: Jim S on February 21, 2003 05:16 PM

Must... control... fist... of... death...

:)

Posted by: scott on February 21, 2003 05:42 PM

Pat's rule #1 You have to help your Mom. That is also Pat's rule # 1-100 lol

Posted by: Pat on February 21, 2003 05:55 PM

Yeah, I'm getting that wonderful experience now that I'm a contractor and we have to take care of idiots the world over now.
At the shooting point, I act like the phone is going dead and hang up on them, then make like a tree and leave (running from the office, telling no one where I'm going).

Posted by: Cindy on February 21, 2003 11:00 PM

Not to trail too far off the subject, but I always thought it would be easier for tech support to help customers if the techie could SEE what the person calling is doing somehow. Sitting there while the computer user tries to explain what he's seeing-- "The thingy with the whatsis just popped up a whosits...."

If you think it's nervewracking for the techie, imagine how it feels for the computer owner. It really is like one blind man trying to tell another blind man how to defuse a bomb....

Let me testify, THIS is running thru your mind constantly: "Oh crap, I paid a fortune for this thing, all my work/my partner's work/my boss's work is on it, I barely understand how it works, I have no idea what I'm looking at, if I scramble it up I am utterly screwed for the rest of the millenium, and this guy's giving instructions to me in Sanskrit !"

From my angle, the whole setup is insane. I mean, if a garage tried to fix your car by giving you instructions over the phone, they'd go out of business. But it's perfectly acceptable and normal practice for a machine a kazillion times more complex!

Of course, a lot of things about the computer industry are utterly buggered up.
Imagine if cars were like computers.
For instance, imagine having to buy a new carburetor for your car... but when you go in and hand over your cash, you're required to sign a waiver releasing the parts store and the manufacturer from any liability if it blows your car up....

... you go and buy a car, you have to buy the brake, clutch, and gas pedals, the stick shift, the dashboard meters and the steering wheel seperately.... and although there are hundreds of auto maker, there are only two steering-wheel set manufacturers. One produces a steering wheel combo that's easy enough for anyone to use, but it causes your car to crash every few thousand miles--- the other produces a steering wheel that never crashes, but you need to entirely relearn how to drive your car to use it (but it comes with a nifty penguin air freshener.) And if you install it, your car radio, CD player, air conditioner and cup holder no longer work.

If you don't get new parts for your car every so often, your trunk space starts to shrink, you lose gas mileage, and you can no longer get up to standard highway speed.... and eventually you have to buy a new car anyway, because they stop making parts for it two years after they put it on the market.

The damn car would catch engine troubles from other cars in the parking lot....

And to top it all off, you would have to buy extra engine components for *every single thing* you wanted your car to do.

Posted by: RHJunior on February 22, 2003 02:02 AM

Not to trail too far off the subject, but I always thought it would be easier for tech support to help customers if the techie could SEE what the person calling is doing somehow. Sitting there while the computer user tries to explain what he's seeing-- "The thingy with the whatsis just popped up a whosits...."

If you think it's nervewracking for the techie, imagine how it feels for the computer owner. It really is like one blind man trying to tell another blind man how to defuse a bomb....

Let me testify, THIS is running thru your mind constantly: "Oh crap, I paid a fortune for this thing, all my work/my partner's work/my boss's work is on it, I barely understand how it works, I have no idea what I'm looking at, if I scramble it up I am utterly screwed for the rest of the millenium, and this guy's giving instructions to me in Sanskrit !"

From my angle, the whole setup is insane. I mean, if a garage tried to fix your car by giving you instructions over the phone, they'd go out of business. But it's perfectly acceptable and normal practice for a machine a kazillion times more complex!

Of course, a lot of things about the computer industry are utterly buggered up.
Imagine if cars were like computers.
For instance, imagine having to buy a new carburetor for your car... but when you go in and hand over your cash, you're required to sign a waiver releasing the parts store and the manufacturer from any liability if it blows your car up....

... you go and buy a car, you have to buy the brake, clutch, and gas pedals, the stick shift, the dashboard meters and the steering wheel seperately.... and although there are hundreds of auto maker, there are only two steering-wheel set manufacturers. One produces a steering wheel combo that's easy enough for anyone to use, but it causes your car to crash every few thousand miles--- the other produces a steering wheel that never crashes, but you need to entirely relearn how to drive your car to use it (but it comes with a nifty penguin air freshener.) And if you install it, your car radio, CD player, air conditioner and cup holder no longer work.

If you don't get new parts for your car every so often, your trunk space starts to shrink, you lose gas mileage, and you can no longer get up to standard highway speed.... and eventually you have to buy a new car anyway, because they stop making parts for it two years after they put it on the market.

The damn car would catch engine troubles from other cars in the parking lot....

And to top it all off, you would have to buy extra engine components for *every single thing* you wanted your car to do.

Posted by: RHJunior on February 22, 2003 02:02 AM

http://rinkworks.com/stupid

enjoy ;)

Posted by: Pam on February 22, 2003 05:03 PM
Post a comment
Name:


Email Address:


URL:


Comments:


Remember info?