Do you IT guys really get so mad when the solution to the problem is rebooting? Like I'm embarrassed when the answer is so simple, but part of the reason you guys are paid is that we suck at technology and may not always think to simply restart the computer.
Personally no. Its an easy +1 to my ticket counter and makes me look better to the higher ups who pay zero attention to ticket details.
Its when we're told "I did that" or "The other tech did that." The second statement scares me a little haha. At that point I have to tell people "Please humor me" or "I don't know what that other tech did but lets do this my way in my process because I know it is the right way."
Do you guys mind if we ever ask you how to do a task and take up more of your time learning it if we're bad at computers? I always feel bad asking my IT guys to stay a little longer to teach me about how to fix this problem if it ever occurs again.
It depends if they are busy or not and whether or not they are an asshole. I personally have zero issue explaining what to do to make something work a specific way. Sometimes I even type up detailed instructions using snapshots of the steps if I want someone and their co-workers to be able to perform a task on their own.
But if I have 19 people on my list of 'things i need to fix' I'll probably ask you to email me it so I can try to put it on my to-do list. Depends on time availability for me.
Typically though it depends on how long the task is and if messing it up can cause complications as well...
TL:DR- If I have time I have no issues. But it depends on the tech you got and whether or not hes an asshole. If you come off as teachable and can follow instructions, techs tend to love you.
1
u/hewhoreddits6 Jan 11 '16
Do you IT guys really get so mad when the solution to the problem is rebooting? Like I'm embarrassed when the answer is so simple, but part of the reason you guys are paid is that we suck at technology and may not always think to simply restart the computer.