How to Give an IT Geek a Stroke

tags: , , , , , , , , ,

The moral of this short video is this: never bring a magician on a tour through your facilities. Or, if you do, don't curse on camera when this magician destroys something you've spent hours setting up.

Okay, here's the link: i.

More like this

tags: Eduard Trololo Khil, Encounter over Planet Trololololo, Star Trek, parody, funny, humor, fucking hilarious, television, streaming video If you watched this video, then you've already seen a little of the newest meme to take youtube by storm. But someone tracked down the real singer in that…
tags: Downfall, Even Hitler Made a Hitler Parody, internet meme, technology, Hitler, satire, parody, humor, comedy, fucking hilarious, streaming video If you've been following the Hitler Parodies video meme on YouTube (197 unique videos so far!), then you'll appreciate this amusing parody where…
tags: Finnish Father Christmas, Santa Claus, Jack Bauer interrogates Santa Claus, comedy, humor, funny, fucking hilarious, holidays, Christmas, Finland, streaming video Here's another video documentary that reveals the travails that Father Christmas encounters when he tries to enter the United…
tags: Late For Work, jobs, employment, humor, funny, comedy, fucking hilarious, social observation, streaming video It's hot, you were up late drinking with your friends and now it's Monday morning -- again! Unlike some videos that I share with you, this one gets straight to the point -- a point…

I'm sure it works nicely, but it requires a rather large amount of talent and effort.

I prefer the old-fashioned way of giving an IT geek a stroke - by simply providing ample supplies of Mountain Dew and Cheetos.

By Phillip IV (not verified) on 26 Feb 2010 #permalink

In most systems (with less redundancy than that) the IT geek is visualizing threading in a new cable with both hands while fending off calls from outraged users and having to explain the whole thing to his boss. He apparently didn't know the guy was a magician.

Reminds me of a couple of instances in my career with tricky wiring.

The first was 1994 at Brown University. Cleaning up a bunch of dead copper behind the Data General MV9600U, and I start hearing the console beeping. I come around to the other side and see the volumes dismounting:

"Gretel dismounted"
"Hansel dismounted"
"Witch dismounted"

I look over at the disk array just as my boss whips into the computer room. He had that red knot on his forehead. Turns out I managed to pull a cable past the locking hubbel connector that powered the disk array. It rotated just enough to break power.

Twisted it back in and everything was good. Got my first lesson in rebooting ancient hardware. I still remember the command "B 24".

Year later I'm working for the state. The network patch is a rats nest. I make the decision that my network guy and I will re-wire it. Hadn't planned on my net guy being a mensch and bringing two six packs of Bass Ale with him.

It got re-wired but we spent the next day patching things up.

Ok, it's a trick. But in the real world this guy was lucky that the techie responded so mildly.

I don't care how much redundancy you have, this sort of thing (if real) can cause real damage. It takes time for a system to fail over; and that costs money. When you also consider that some systems won't fail back after repair, or won't stand two points of failure, inducing something like this imposes real - monetary - risk.

Personally, I would have escorted him from the room immediately and had him arrested for criminal damage.