TexBlog

Steve Teixeira's Blog -- Thoughts on parallel computing, Microsoft, the industry, and life

The superstition of broken computers

The superstition of broken computers

  • Comments 14

If you're reading this, odds are that you're the family IT guy/gal as well.  Like me, I'll bet you field calls from all over the country about web browsers and email and spyware and viruses and the like.  And, God help you if you work for Microsoft because then even what is normally the last refuge of the family IT person ("Beats me.  You should call Microsoft.") is unavailable to you.

As mellow-harshing as it is helping Mom with her IM problem or Gramps with his email filtering rules, I have to say that my worst client by far is my wife.  Don't get me wrong; I love her dearly.  But make no mistake; she is the family IT guy's client from hell.

I actually think I could cope with her insistence on five 9s of uptime on her Dell laptop if it weren't for her persistent opposition to how I try to maintain that uptime.  For example, I'm pretty anal retentive about keeping all of the software on the family computers up to date.  For Helen, each of these regular tune ups is just another opportunity to break what she views as a perfectly functional computer.  Take this recent conversation, for example:

Steve: Clickity, clickity, click, click...
Helen: "GAAAAAAA! What are you doing??"
Steve: "Um, I'm updating your iTunes software."
Helen: "Why are you messing with that? Every time you update my computer it breaks for like two weeks."
Steve: "No, keeping your software up to date is actually what keeps it running reasonably reliably."
Helen: "No way! Every time you install those damn updates something breaks.  It's running fine, why don't you just leave it alone?"
Steve: "It's running fine precisely because I don't just leave it alone."
Helen: "Whatever.  Have fun.  I'm just going to use the computer in your office for, like, the next 19 hours straight."
Steve: Makes angry noises like Muttley.

When Helen's laptop appeared to go on the blink over the past week or so, you might say that she casually mentioned it to me once or twice.  You know, just in passing.  Anyway, as I tried to diagnose the issue, Helen watch carefully that I didn't make the problem worse with one of my hair-brained updates.

I'm not going to lie to you.  It felt pretty good to trace the problem to a slightly overheating wireless access point (small aside: of all things! imagine!) and point out that, once again, my much maligned updates were not the cause of her problems.  Some words may have been said at that time, possibly including something about "in your face" and "Flanders."

Anyhow, in the midst of this most recent conversation, it hit me: Helen isn't a computer expert, so she's looking for a causal relationship between *something* and her computer problems.  She a perfectly capable computer user, but she doesn't really know or care how they work.

Curiously, she didn't appreciate it when I pointed out the eerie similarities between her insight into the workings of her PC and cavepeople's insight into their world.  Cavepeople, for example, knew about the weather and how to deal with hot, cold, wet, or dry times of the year.  But they didn't know how the weather worked, so they probably operated in no small part on superstition.  The conversations may have gone something like this:

Thag: "Hmmm. Five large birds fly away from sun.  Mean snow come soon."
Grog: "Thank God it not six birds.  Me hate pterodactyl egg-size hail."

Helen demonstrated her appreciation for my keen observations here in her customary way, although more of the hitting seemed focused on the ribcage area this time.

I guess the moral of the story is that breaking a mirror will not only lead to seven years of bad luck, but its a surefire omen that a nearby hard drive is about to crash.

  • Maybe she as a point, as they say: "If it ain't broken don't fix it" :)

  • Nice post. Good use of the narrative. Picked a topic both geeks and non-geeks can relate to. AND it has a beat I can dance to. I give it a seven out of ten.

  • Et tu, Luciano?  :)

    Thanks, Chaim.  Next time around I hope to score the mythical 10/10.  :)

  • IT'S BEEN BROKEN FOR A MONTH, FIBBER! And it's still not fixed! I don't know what you're all smug about over there. AND IT STARTED WHEN YOU INSTALLED THE UPDATES. AS USUAL!

    I AM NOT THE CLIENT FROM HELL! I just demand excellence! No down time!

    I'm still in your office. And I'm staying here until it's fixed.

    And like all angry actresses, I'll be in my trailer! <slam>

  • Mmm hmm.  Oh, wait, hang on... phone's ringing...  It's Lindsay Lohan.  She calling to say she needs her attitude back by 3:00 today. Mmm-kay?  ;)

  • Wednesday, October 18, 2006 7:52 AM by Luciano

    > Maybe she as a point, as they say: "If it ain't broken don't

    > fix it" :)

    Yup ... and maybe she learned that point from reading too many Knowledge Base articles ^_^

    Though actually there is a point, when installing an update, be prepared to uninstall when necessary.  NT4 SP4 did cause a lot more blue screens than NT4 SP3.  I've had computers where Windows 2000 caused more blue screens than Windows 98 (though less than the frequency of blue screens that applications could cause under Windows 98).  Some bug fixes have been retracted because they added worse bugs than they removed, and some others weren't retracted but should have been.

  • I agree with your wife.  My ex husband used to talk me into upgrading my machine (new OS, new hardware, whatever).  He'd swear that it would only take a little bit of time, and then it would run SO much better.  Invariably I'd be without my computer for a few days, and he'd be losing a lot of sleep trying to get it fixed.  I remember fondly the time he fell asleep in a chair with the keyboard on his lap...

    Keep in mind that I too, am a geek -- I've done helpdesk work for almost 8 years now; if I've learned anything, it's that "if it ain't broke, don't fix it!" applies to computers as well as it does to anything else, if not more so.

  • Norm: I believe we've gotten a lot better about updates since Windows NT 4 days.  However, you have a point that an update can introduce a regression on occassion.

    Michelle: I hear you, but I'm not talking about major new OSes and hardware in my case.  I'm talking about security updates, mostly.

  • Good post.

    I don't work at Microsoft and there is no way I'd suggest calling the OS vendor to solve any problem.  

    But, can I have my family call you when something goes wrong?  ;)

  • Robert: Sure, it seems like everyone else does.  :)  I even did tech support earlier in my career, so I'm well prepared.

  • > I believe we've gotten a lot better about updates since

    > Windows NT 4 days.

    I don't.

    In Windows NT 4 days I seem to recall Windows NT 4 customers being treated better than Windows 98 customers, in terms of having hotfixes downloadable.  (Though that didn't help enough because it was impossible to buy a computer with NT 4 preinstalled instead of 98, except on a very limited selection of hardware which was essentially crippled.  Also in the Japanese product, NT 4 SP5 and subsequent didn't completely repair the damage that NT4 SP4 caused.)

    With Windows XP and 2003 there have been a lot of hotfixes for which Microsoft wouldn't allow downloads without first opening paid support incidents.  (I've read that in some countries Microsoft would listen to the Knowledge Base article numbers and provide hotfixes without paid support incidents.  I don't live in one of those countries.)

    With Visual Studio 2005 the same policy continues.  So I really wonder how you can think this is an improvement from Windows NT 4 days.

  • AH HA! So people agree with me! Take that, Geek Boy! ;)

  • Can you please pass the popcorn, the show is too good to leave.

  • Hopefully you now see how unreasonable Helen is about change, given her recent implosion at the wordpress UI refresh.  :)

Page 1 of 1 (14 items)