PEBKAC

[Abbrev., "Problem Exists Between Keyboard And Chair"] Used by support people, particularly at call centers and help desks. — The Jargon File

Why it’s better to pretend I don’t know anything about computers.

For all those planning to ask me to fix their computers this holiday season, please read this wonderful parable.

And if you really do want your computer to run fast:

  • Stop using Internet Explorer.
  • Stop downloading crap.
  • Keep the kids away from your computer.
  • Buy as much RAM as you can cram into the thing.
  • Keep a selection of nut-free cookies on hand for when I turn up to work on your computer anyway.

The Amazingly Adaptable Human Brain: The Case of the Contrariwise Computer Mouse

Unmighty Mouse

After fifteen years in the computer industry, I am used to this — proudly delivered — declaration: “Oh, I don’t know anything about computers.” Immediately following, this computationally illiterate individual proceeds to show me seven different things I never knew a computer could do.

And then there are people like George (name changed due to my forgetting what it was originally — it might’ve even been “George”) who show me something I didn’t know humans could do.

At the time, I was working as a programmer in the Information Technology department of a Bay Street investment house, and every so often I would be asked by one of the computer system users to watch them demonstrate a bug in the program, or a new feature they’d like to have implemented.

George was new to the company, also seemingly new to computers, and asked me to witness some problem he was having with the system. I elevatored up to meet him, and he began his demonstration, as users invariably do, by showing me how he normally launches the program, logs in, and navigates to the screen causing the problem.

Usually, this part of the demonstration is very tedious: I know how to launch the program, log in, and navigate to the screen — had done it a thousand times myself. But then I noticed something quite unusual.

George was holding the mouse upside-down.

Not upside-down as in the ball was pointing up (mice had balls back then, tee hee), but upside-down as in the buttons were under the heel of his palm, the cord winding along beneath his cuff until it dropped over the front edge of his desk.

I watched as George clicked screen menus and buttons using his thumb. Awkward doesn’t begin to describe how one must contort to thumb-click the mouse’s right button when it is positioned under the left side of your right hand’s palm. Even describing it is awkward.

More astounding was that George was moving the mouse in exactly the opposite direction from what you’d expect. To move the mouse pointer up, his hand shifted down; to move the pointer right, he rolled the mouse to the left. It was as though the cursor was fixed on the screen and he was sliding the virtual desktop underneath it until the pointer was positioned as he intended — difficult to visualize, but out-and-out disturbing to witness.

At this point, I realized that George had stopped speaking and was looking at me with a raised eyebrow. He had been narrating his progress through the system’s screens and must’ve reached the problem area while I was lost in mouse-gesture wonderment. I apologized and asked him to repeat his demonstration from the beginning; I couldn’t help myself.

When it came time for me to use his computer, I made a pointed dramatic rotation of the mouse, but refrained from mentioning the accepted mouse orientation aloud. When I was finished, I left the mouse upside-up, but as I left the room, I noticed that he had returned it to his preferred position.

Upon hearing my report, a couple of others from the department snuck up to George’s floor a few days later to spy on him and his mouse from over top a neighbouring cubicle wall. He was still up (down?) to his inverted tricks, double-thumb-clicking with abandon. We developed the theory that, because his desk was pushed against a wall, the keyboard and mouse cords had been routed over the front edge of his desk to the computer underneath, and that the weight of the cord had pulled his mouse upside-down. Unfamiliar with these newfangled computer doohickeys, George had simply adapted his muscles, joints, and brain to the working environment as he found it.

So George, we salute you, for showing us all that, no matter how mentally and physically contorted we all feel when trying to use computers, it could be much, much worse.

How to buy three chairs.

On March 5th I got a note that one of the computer labs in the College was minus three chairs. They were borrowed or mangled or misplaced or had succumbed to any one of a hundred other misfortunes that can afflict the modern office chair.

As the person ultimately responsible for the computer labs, it fell to me to order their replacements.

Now I should tell you: I had never ordered a chair before. Oh, I could order computers blindfolded, and network switches on tiptoe, and even drafting software while downing a dagwood, but never a chair. So each and every one of the following bureaucratic bungles are either beyond the realm of mortal control, or are entirely my fault.

My three-chair order eventually required:

  • Two requisition submissions;
  • One requisition denial for incorrect account numbers;
  • One requisition denial for falling under the low value purchase limit;
  • One requisition resubmission after the total of the three exceeded the low value limit;
  • Three minutes of on-site visit by…
  • Two office furniture company representatives to determine the correct chair model (I described them on the phone as “bendy, black, and with elbow platforms”);
  • One discovery that this precise chair model was on back-order; and
  • One last-minute purchase order cancellation because the purchase order had already been issued by a different department a week earlier.

The chairs arrived today, May 4th, just a hair under two months after the initial request. Now I just have to assemble them.

How long could that take?

Technical Support Free Verse

While debugging an errant process in the College’s execrable system this afternoon, I found this passage in a technical support bulletin from the manufacturer:

“After step 1 is complete; which the system will not allow you to
accomplish completely; all the TBRAPPL transactions should have a
reapply indicator of Y.  We know this will not be the case in your
situation.”

It’s a fricken’ Zen koan: the true completeness is that which is incomplete; that which should be is that which will not be.

Local programmer’s WTF moment hits the big time.

The Daily WTF recently posted an entry named “The Mostest Wrong Datatype” which seems — pure coincidence, surely — to refer to a local programmer of your acquaintance.

The WTF site highlights examples of confused, inexplicable, or just plain awful programming code. (If you’re not of the technical persuasion, you may still enjoy the Error’d portion of the site, which features amusing shots of bewildering computer screens.)

By the way, if you happen to be one of the contractors named in the piece: a pox on your house!