Born yesterday

I wasn’t born yesterday, and neither were you.

When you call me with a problem and tell me that you “don’t remember” what you did, I know that isn’t true. I know that when I arrive, it will be obvious what you did. You tried something, it didn’t work, and now you’re embarrassed to admit that you’ve gotten stuck. However, the best ruse you can devise to avoid this apparent embarrassment is to tell me you “don’t remember”.

Newsflash:

Claiming you “don’t remember” something you did 3 minutes ago makes you sound like an idiot. Or potentially the protagonist from Memento. Mostly, just an idiot. Certainly much more of an idiot that someone who actually tried to work something out for themselves, which is what you did. Just because you got out of your depth doesn’t make you look foolish. Claiming you have a lesser mental capacity than a 9 year old? That does.

About The Angry Technician

The Angry Technician is an experienced IT professional in the UK education sector. Normally found in various states of annoyance on his blog. All views are those of his imaginary pet dog, Howard.

3 responses to “Born yesterday”

  1. A Fellow Tech says :

    This is usually combined with outright lying about what they did/didn’t do, and glazed over eyes as you try to explain anything. The main issue is you showed up to help, so they feel like they were successful in the game of “get the tech to do it”.

  2. ICT_Tech says :

    ID:10T Error

    we get that all the time

    Just been to computer that ‘wasn’t working’, it’s amazing how things start working when you plug in things like the network cable!!

  3. ScottishTech says :

    When I’m rolling out a multicast disk image to 20 workstations and the PC which has been the multicast master curiously throws up a -99 error on the console, causing the other 19 to abort (God bless you, Altiris and your peculiar multicast technique), it causes me upset.

    When I walk to the other end of the school to find that the Multicast Master PC is sitting with the Windows boot error screen which crops up when you reboot a PC mid-disk image rather than the Altiris disk imaging boot disk, it raises curiousity in my mind.

    Oh, hello there Teacher who normally works in that room. Yes, you, skulking in the corridor avoiding any form of eye contact. Did you happen to click the EXIT button?

    No?

    Are you sure?

    Are you REALLY sure?

    Alright – calm down. I merely asked if you clicked a button, not if you were responsible for a steaming great Guinness-scented turd on the floor. I’m just trying to do some diagnosis.

    If you didn’t click EXIT, then it means that the hard drive is probably borked since that’s the usual cause of such a thing happening. Or possibly the RAM. Either of which means I have to walk back to the other end of the school, source replacement RAM and HD, walk back and plug ’em in before I can resend the job.

    Now… Are you REALLY sure you didn’t click EXIT?

    Ah, so maybe you might have given the mouse button a teeny tiny little insignificant click while the pointer was hovering near one of bit of the screen (but you can’t remember which bit. Or which mouse button)..

    No, no that’s no problem. I appreciate your (slightly delayed) honesty. That’s fine, off you go home. Enjoy your evening. Just mind your feet when you come in tomorrow morning.