今天收到一封我訂閱的電子報，裡面有一個文章我看了還蠻有趣的，就是10個惹毛資訊人員的方法，前面的描述我就不說了，原來中外皆然，惹毛資訊人原的方式差不多，還蠻有趣的，截錄原文如下
Top 10 Ways to Piss Off the IT Guy:
1.Fail to mentions problems during normal work hours but always bring them up on breaks, at lunch or 5 minutes before closing.
在正常工作時間內不反應問題，都是在下班前或是吃飯前5分鐘才說有問題(會跟你說問題已經發生了幾個小時)。
2.Be too lazy to write an email of a problem but call the IT guy over when he is walking by – obviously on the way to solve a separate problem.
懶的寫信給資訊人員，但是資訊人員從旁邊過時會叫他們，卻是解決一個顯而易見的問題。
3.Assume that your issue is the most important one and that the IT guy will drop everything right away to fix it.
假設你的問題非常重要，資訊人員必須停下手邊的工作，馬上去處理你的問題。
4.Become irritated when a problem is not solved right away – believe it or not, a certain amount of time is needed to solve every single problem.
一直煩資訊人員處理一個需要時間來解決的問題(EX查資料需要時間，但是一直打電話來問問題處理好了沒)
5.Attempt to fix a problem yourself (thinking that you’ll save the IT guys some time), only to make the original issue even worse.
自己試著解決問題，但是讓問題越來越複雜(越來越糟)(資訊人員最怕自以為資訊能力很強的人，生手或是熟手都不怕)
6.Email your IT guy with a non-descriptive, super-general statement about a problem such as, “my computer won’t work”.
寫信給資訊人員，卻不描述問題(EX:就寫我的電腦不能印，但是不講什麼系統不能印，什麼情況下不能印)
7.Assume that the IT guy is aware of every issue – even when nobody has brought it to his attention.
假設資訊人員已經發現每個問題，但還沒有人發現這些問題。
8.Assume that every technological issue that arises is somehow the fault of the IT guy – sometimes it is, usually it isn’t.
假設每個發生的技術問題是因為不良IT人員造成的，有時是，但通常不是。(EX:你們菜鳥工程師是不是動了什麼造成系統問題…..暗~那個東西是我在管控的)
9.Call the IT guy instead of emailing him and start your first sentence with, “this isn’t a big deal but…”. Then why are you calling?!
寫信給資訊人員，說這不是一個大問題，但是…那你幹麻寫信給資訊人員
10.Make every issue sound like its the end of the world – it only makes the IT guy realize that none of your issues are really that important.
把資訊問題說的好像是世界末日，這只會讓資訊人員認為你的問題不是那麼的重要。