Why it Sucks to be the IT Guy [Comic]


----------------

Yes, being the IT guy often totally suck, and after working for 15 years in the field, I can confirm that most of what is in this infographic is unfortunately all too true, especially the part about what people expect from us in our everyday job.



[Source: ORSYP]







14 Responses to Why it Sucks to be the IT Guy [Comic]

  1. That’s a bunch of BS.

    I have almost no sympathy for the plight of the IT guy for my company.

    His solution to EVERY problem: Restart the program. If that doesn’t work: Restart the computer. If that fails, it’s: Unplug the computer and start it back up.

    Then, if I call with an issue he might add: “Huh, that’s something I haven’t seen before.”

    I started out as a computer science major (turned journalist/editor/page designer) so I try to give him as much relevant information as possible, but it’s often for naught.

    Me: Do you think it needs an update?*
    IT guy: No. There’s no update for it. Try restarting the program.
    (20 minutes later)
    Me: It’s still doing (or not doing) the exact same thing.
    IT guy: Let me see if there’s an update.
    (20 minutes later)
    IT guy: There’s an update for that. You’re going to have to restart your computer.

    *The computers are locked out so we (us peons) can’t do the updates ourselves.

    • I hate that on every article like this, there is always one person posting an anecdote like this. We get it. Every profession has useless people doing it wrong, and IT is no exception. That person is not who this article is about… There are thousands of us who can relate and empathise quite well with this.

    • Just because you had a bad experience with ONE PERSON, that doesn’t make this post BS. One bad IT guy doesn’t make all IT guys bad. Quit your whining, you baby.

    • Even if you don’t have an admin account, as a “computer science major” you should be able to figure out both the root of the issue and the availability of a patch before you call …

    • The majority of people will make suggestions/posit solutions/claim to have already done standard troubleshooting, and they’re idiots, liars, or both, so your IT guy *has* to assume that you know nothing and have tried nothing until he can verify that you’ve done the “turn it off and on again” and so forth. Just because you know that you have some knowledge does not mean he can automatically assume you know as much as him, or won’t try to cut corners like every other person in the building.

      Support methodology dictates that he try the least invasive solutions first – off&on etc. – then gradually move up the scale through updates, settings, and eventually hardware. That’s so that he doesn’t wind up spending half the day peering at fan cables because you accidentally left your caps lock on or something equally productive. He cannot deviate from that methodology because it would result in much more wasted time than you spending twenty minutes restarting your kit.

      Essentially, while your IT guy sounds like a jaded shell of a man who may not be fun to be around during working hours – possibly due to dealing with so many of the muppets mentioned in the article – his methods are perfectly correct, no matter how much of an under-appreciated IT guru you seem to think yourself (and yes, if you know enough to suggest an answer and expect him to arrive at it instantly, then don’t say “do you think there’s an update?”, but “a new update was released Tuesday and hasn’t been applied yet, can you see if that will fix it?”).

    • Back in the old days in the late 90’s I used to tell people to run scandisk and defrag on windows 95 and that would buy me 1-4 hours sometimes. I can understand the “restart the computer” idea because fortunately it does fix some problems when people leave their computers on all week.

  2. Erm… an IT guy had to have made that…. Leaving the “strained to meet deadlines” phrase a little out of the water… Strained to meet deadlines because he was working on an arty poster which basically calls EU c**ts constantly making Id10-t errors.
    To save time; USERS, most of your problems are created by you! Don’t get pissed when i have to ask 56 times what you’ve done then eventually have to guess because you lied anyway

    • Not necessarily true: I’m no IT guy, but I pretty much knew that all of this goes on. Maybe a graphic designer with friend(s) in IT made it?

  3. I wouldn’t let you (the end user) do any updating or installing software on your PC either, though I’d damn sight do a better job of keeping you up and running. Not every IT guy is a total slackapotamus, but the vast majority of end users should never be allowed under the hood. Restrictions on your company-owned PC exist for a reason.

  4. I apologize, perhaps I’m being too much of an asshole.

    After reading the comments and re-examining the illustration, perhaps I’m being a bit too hard on the IT guy. The computers we use are Macs and while I understand and prefer PCs I can see why there’s a blanket restriction on updating the software.

    After all, a few years back some other folks in the company saw it fit to set up one of the computers to be the main download station for pirated music. What happened after that was whole series of corrupted machines (we had to replace all the computers in the company).

  5. I feel bad for the IT help desk guy SOMETIMES. Dropping of my machine to get rebuilt once a year shouldn’t be a big deal. If it takes 3+ days t do it = FAIL.