"10 dirty little secrets you should know about working in IT"

M

moetop

[H]ard|Gawd
Joined
Apr 8, 2004
Messages
1,471
Found this and thought some others here might find it interesting...
10 dirty little secrets you should know about working in IT

I don't find all to be absolute, but I do see some truth to them. I have seen #4 be a double edged sword (insert curse words and CiscoWorks here :) ) It's mostly the perception that tools like that are supposed to help you do your job, but in reality they are just another system to support that creates different work, hopefully less, but not necessarily. (i.e. now management wants the cool reports that it can generate.)

The details of each are at the link.

10.) The pay in IT is good compared to many other professions, but since they pay you well, they often think they own you


9.) It will be your fault when users make silly errors


8.) You will go from goat to hero and back again multiple times within any given day


7.) Certifications won't always help you become a better technologist, but they can help you land a better job or a pay raise


6.) Your nontechnical co-workers will use you as personal tech support for their home PCs


5.) Vendors and consultants will take all the credit when things work well and will blame you when things go wrong


4.) You'll spend far more time babysitting old technologies than implementing new ones


3.) Veteran IT professionals are often the biggest roadblock to implementing new technologies


2.) Some IT professionals deploy technologies that do more to consolidate their own power than to help the business


1.) IT pros frequently use jargon to confuse nontechnical business managers and hide the fact that they screwed up.
Click to expand...
 
I'm not an IT "Professional" by any stretch, but using "jargon" to confuse my General Manager is something that I literally wait for in my day at work.

It is so amusing to see him when I told him our servers were down because "NOD 32 didn't catch a worm in our POS station."
 
#11.) Workers will see you as a prick because you've prevented them from doing shit on their computer which they know they shouldn't be doing anyway.
 
12# In networking. Its ALWAYS a network problem. Of course until you give em a capture or a report that tells that it not the fucking network.

13#PBX guys will always blame the network for isues with their PBX system. Eventhough it's that piece of shit Avaya that is causing problem.
 
3 ... how true, how sadly true.

I am 'newish' to the field in which I have grown up studying all of the current best practices and technologies; trying to implement them is next to impossible with all of the legacy egos.
 
The first rules in my IT Dept:

1) Vendors lie
2) Managers believe vendors

The rest of that list is good though.
 
unix_foo said:
12# In networking. Its ALWAYS a network problem. Of course until you give em a capture or a report that tells that it not the fucking network.
Click to expand...

+1 on the #12

run into this everyday, the server guys always blame the network, then.. "oh I need a Default GW configured?", LOL
 
XOR != OR said:
The first rules in my IT Dept:

1) Vendors lie
2) Managers believe vendors

The rest of that list is good though.
Click to expand...

That's how we got suckered into using McAfee who all of us in Infrastructure support hate. We pushed hard for NOD32 and Kaspersky and got neither because someone on McAfee's sales team was a smooth talker.

solotech said:
I like 1 and 3..

All PBX's should burn and die.. Long live IP!
Click to expand...

Bumping this for jeffmoss to read. QFT! :)

Just wanted to add one more secret -- Help desk and desktop support are usually treated like dirt by other IT personnel. Ok, that's not a secret. lol
 
All I can say is thank fu*k its not just me who has all these issues.....

To be honest this list makes me feel good to know I'm not alone.

Thanks :D
 
4.) You'll spend far more time babysitting old technologies than implementing new ones
Click to expand...

What a suprise, this is exactly how the IT guy is at my school. In his mind "Why use racks and label
things when I can set everything on the floor and have wires going everywhere".
Fun when the "CAD" computers crash because of their mx440, 512mb ram and microsoft video drivers.
What a suprise that he doesn't let anyone else touch anything $%#$%. Would be fun to help out and learn
a thing or two but no...
 
#1 reminds me of the old Dilbert cartoon where he had the PHB snooping around on the floor looking for the token that fell out of their cable in the TR network.
 
10.) The pay in IT is good compared to many other professions, but since they pay you well, they often think they own you
Click to expand...


9.) It will be your fault when users make silly errors
8.) You will go from goat to hero and back again multiple times within any given day
Click to expand...
I often find if I can prove a user is wrong- it works.
I've had problems with applications crashing due to users not properly exiting them (proprietary apps- what can you do?). Or not exiting them at all (leaving it running on the network idle).
Simple fix? Take screenshot of proof. Email reminder to user- with proof right there.

Instead of denying it as usual- they keep quiet, realize you can make them look like a jacka** next time you bring an issue with what they are doing to their attention (because remember- you can prove them wrong!)


6.) Your nontechnical co-workers will use you as personal tech support for their home PCs
Click to expand...
Luckily I don't get this a whole lot (Very very picky about who gets my personal cell # and email address)...
But it has been a problem in the past. Everyone thinks they get free help. Family is the worst.
The worst part about it is that they don't learn from mistakes- and expect you to fix it again.

5.) Vendors and consultants will take all the credit when things work well and will blame you when things go wrong
Click to expand...
So freaking true...
 
#14: Never under estimate a managers desire to look good regardless of what is right, and what is even fscking technically possible.

i.e. "The CEO wants to get his email while climbing Mt. Kilimanjaro, I told him it could be done. See what we need to do."
 
unix_foo said:
12# In networking. Its ALWAYS a network problem. Of course until you give em a capture or a report that tells that it not the fucking network.

13#PBX guys will always blame the network for isues with their PBX system. Eventhough it's that piece of shit Avaya that is causing problem.
Click to expand...
QFT! wow, are you sure you don't work on the same team as me? :p

The network is magical, it just somehow works... and when something doesn't... blame the network!!!!!
 
love the network one :D i look after our network and servers, whenever one of our apps is slow / not working the developers always blame the server or network, 99 out of 100 times its the app!
 
what about

You can never get funding for your fantastic idea unless you make your manager think it was their idea in the first place.

or

No matter what, a user will call you about a problem even though the last 100 times they caused the problem a simple restart of their system has fixed the issue.

or

IT workers are proactive, they like to replace equipment before it fails, MDs and board members are reactive they like to replace things once they have gone on fire or killed some one but if there is a network outage (and the Managers can't get on the net to look at shoes and pictures of their friends baby) there is uproar and th MD and board ask "Why did this happen?"

or

The buget is always tight for IT equipment but some how the MD can go and buy two boats in one day in different parts of the world.

or

People who don't have a clue about IT, how a network works or even where the server rooms are have more say in meetings than you.

and the one that really annoys me.....

Because you know about computers people think that you will also be able to fix photocopiers, phones etc.

I will finish this post with a 100% true quote from the MD

"I know its not possible but I want you to do it."
 
Jay_oasis said:
No matter what, a user will call you about a problem even though the last 100 times they caused the problem a simple restart of their system has fixed the issue.
Click to expand...

lol... Or...
No matter what, a user will call you and not try a single troubleshooting step on their own (restart Outlook for crying out loud!).


IT workers are proactive, they like to replace equipment before it fails, MDs and board members are reactive they like to replace things once they have gone on fire or killed some one but if there is a network outage (and the Managers can't get on the net to look at shoes and pictures of their friends baby) there is uproar and th MD and board ask "Why did this happen?"
Click to expand...
Exactly spot-on.
Alot of times the only way to fix this is to have a massive crysis- they learn their lesson- listen to you from now on.

The buget is always tight for IT equipment but some how the MD can go and buy two boats in one day in different parts of the world.
Click to expand...
:D


People who don't have a clue about IT, how a network works or even where the server rooms are have more say in meetings than you.
Click to expand...
:D :D


Because you know about computers people think that you will also be able to fix photocopiers, phones etc.
Click to expand...
LOL

I think your list was even better ;) Every single one I can relate with.
 
I can totally relate... so funny yet so true.

I think the thing that irritates me the most is when our CIO thinks we can just whip together the solution to a problem in a day, promises people we'll get it done and puts us in a mad scramble to make something happen, and then wonders why it breaks (one of his good quotes "Didn't we test this?"). That irritates me to no end....

There should be an IT rule that is Scotty-like, call it the "Miracle Worker" clause, always tell your boss it will take 2x as long as it will, so if it gets done early you look like a Miracle Worker! :)
 
This seems to sum it up:
"We, the unwilling,led by the unknowing,are doing the impossible for the ungrateful. We have done so much,for so long,with so little,we are now qualified to do anything with nothing."-Mother Theresa
 
>>6.) Your nontechnical co-workers will use you as personal tech support for their home PCs

Very true. Coworkers and anybody else that knows you "work on computers".

Reminds me of when the wife of a friend of a friend called and asked me to come over on the weekend to fix her computer. I told her "Sure, have your husband Bob come over and fix my transmission and it's a deal.". Silence on the line and then she says, "Well, he charges money for that, that's his job. Just typing stuff on the computer isn't like fixing cars."

I was about to unload on her, but bit my tongue and politely explained that if he worked on my car for two hours, and I worked on their computer for two hours, they would still owe me money at current market rates.

I then offered my "friends & family rate" of $50/hr if Bob couldn't work on my car. Then she gets mad and says "Nevermind then!" and hangs up. :rolleyes: :D
 
People think working in IT is the same as what they do at home. IT and networks is to home PCs what fixing your home car is to running a F1 team.
 
Spartacus said:
>>6.) Your nontechnical co-workers will use you as personal tech support for their home PCs

Very true. Coworkers and anybody else that knows you "work on computers".

Reminds me of when the wife of a friend of a friend called and asked me to come over on the weekend to fix her computer. I told her "Sure, have your husband Bob come over and fix my transmission and it's a deal.". Silence on the line and then she says, "Well, he charges money for that, that's his job. Just typing stuff on the computer isn't like fixing cars."

I was about to unload on her, but bit my tongue and politely explained that if he worked on my car for two hours, and I worked on their computer for two hours, they would still owe me money at current market rates.

I then offered my "friends & family rate" of $50/hr if Bob couldn't work on my car. Then she gets mad and says "Nevermind then!" and hangs up. :rolleyes: :D
Click to expand...

Nice work! I do hate that though, apparently even though IT people keep the world running, our services should be free :rolleyes:

I must agree with most of the list.
 
Spartacus said:
>>6.) Your nontechnical co-workers will use you as personal tech support for their home PCs

Very true. Coworkers and anybody else that knows you "work on computers".

Reminds me of when the wife of a friend of a friend called and asked me to come over on the weekend to fix her computer. I told her "Sure, have your husband Bob come over and fix my transmission and it's a deal.". Silence on the line and then she says, "Well, he charges money for that, that's his job. Just typing stuff on the computer isn't like fixing cars."

I was about to unload on her, but bit my tongue and politely explained that if he worked on my car for two hours, and I worked on their computer for two hours, they would still owe me money at current market rates.

I then offered my "friends & family rate" of $50/hr if Bob couldn't work on my car. Then she gets mad and says "Nevermind then!" and hangs up. :rolleyes: :D
Click to expand...
http://people.csail.mit.edu/adonovan/dilbert/show.php?day=01&month=02&year=2006

I have run into this a few times. While I don't mind helping people out in general, I do not appreciate being taken advantage of, which often happens in these situations. I have a few trade relationships though that make my life easier; I fix their computer, they take care of all my locksmithing needs ( or plumbing. Or car repair ).
 
I have solved this issue by simply stating, that it is a personal policy that I don't work on peoples home PC's. If they are freinds, I explain that it is nothing against them, as a matter of fact if something ever happend it might get in the way of the freindship.

I just don't do it anymore. (probably the past 4-5 years) For me it's not a matter of the perception of the worth. That is easly handeled by directing them to a good local shop, and when they get the $100-$200+ bill they relize that part of it.

It's more the ownership you take as soon as you touch their PC. Any problem that arizes after that point is somehow related to the problem you fixed before, and you are responsible.
 
XOR != OR said:
http://people.csail.mit.edu/adonovan/dilbert/show.php?day=01&month=02&year=2006

I have run into this a few times. While I don't mind helping people out in general, I do not appreciate being taken advantage of, which often happens in these situations. I have a few trade relationships though that make my life easier; I fix their computer, they take care of all my locksmithing needs ( or plumbing. Or car repair ).
Click to expand...

That's the way to do it, if you're going to do anything. I've made a lot of friends where I am, some of them are VPs. They scratch my back, I scratch theirs. :)

Gotta be careful not to have a large profile if you help out coworkers, especially if you don't actually work for the company you support.
 
You must log in or register to reply here.
Back
Top