Between the Lines

Larry Dignan, Andrew Nusca and Rachel King

10 dirty little secrets you should know about working in IT

By | December 13, 2010, 5:00am PST

Summary: Jason Hiner spills the beans on the most nefarious aspects of working in IT. From bursting the bubble of newbies to explaining how techies cover their butts, here is the tell-all.

If you are preparing for a career in IT or are new to IT, many of the “dirty little secrets” listed below may surprise you because we don’t usually talk about them out loud. If you are an IT veteran, you’ve probably encountered most of these issues and have a few of your own to add — and please, by all means, take a moment to add them to the discussion. Most of these secrets are aimed at network administrators, IT managers, and desktop support professionals. This list is not aimed at developers and programmers — they have their own set of dirty little secrets — but some of these will apply to them as well.

You can also view this list as a slideshow.

http://www.zdnet.com/photos/slideshow-10-dirty-little-secrets-about-working-in-it/491073

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

Although the pay for IT professionals is not as great as it was before the dot-com flameout and the IT backlash in 2001-2002, IT workers still make very good money compared to many other professions (at least the ones that require only an associate’s or bachelor’s degree). And there is every reason to believe that IT pros will continue to be in demand in the coming decades, as technology continues to play a growing role in business and society. However, because IT professionals can be so expensive, some companies treat IT pros like they own them. If you have to answer a tech call at 9:00 PM because someone is working late, you hear, “That’s just part of the job.” If you need to work six hours on a Saturday to deploy a software update to avoid downtime during business hours, you get, “There’s no comp time for that since you’re on salary. That’s why we pay you the big bucks!”

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

Some users will angrily snap at you when they are frustrated. They will yell, “What’s wrong with this thing?” or “This computer is NOT working!” or (my personal favorite), “What did you do to the computers?” In fact, the problem is that they accidentally deleted the Internet Explorer icon from the desktop, or unplugged the mouse from the back of the computer with their foot, or spilled their coffee on the keyboard.

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

When you miraculously fix something that had been keeping multiple employees from being able to work for the past 10 minutes — and they don’t realize how simple the fix really was — you will become the hero of the moment and everyone’s favorite employee. But they will conveniently forget about your hero anointment a few hours later when they have trouble printing because of a network slowdown — you will be enemy No. 1 at that moment. But if you show users a handy little Microsoft Outlook trick before the end of the day, you’ll soon return to hero status.

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

Headhunters and human resources departments love IT certifications. They make it easy to match up job candidates with job openings. They also make it easy for HR to screen candidates. You’ll hear a lot of veteran IT pros whine about techies who were hired based on certifications but who don’t have the experience to effectively do the job. They are often right. That has happened in plenty of places. But the fact is that certifications open up your career options. They show that you are organized and ambitious and have a desire to educate yourself and expand your skills. If you are an experienced IT pro and have certifications to match your experience, you will find yourself to be extremely marketable. Tech certifications are simply a way to prove your baseline knowledge and to market yourself as a professional. However, most of them are not a good indicator of how good you will be at the job.

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

Your co-workers (in addition to your friends, family, and neighbors) will view you as their personal tech support department for their home PCs and home networks. They will e-mail you, call you, and/or stop by your office to talk about how to deal with the virus that took over their home PC or the wireless router that stopped working after the last power outage and to ask you how to put their photos and videos on the Web so their grandparents in Iowa can view them. Some of them might even ask you if they can bring their home PC to the office for you to fix it. The polite ones will offer to pay you, but some of them will just hope or expect you can help them for free. Helping these folks can be very rewarding, but you have to be careful about where to draw the line and know when to decline. For help, take a look at TechRepublic’s free download “Ten ways to decline a request for free tech support.”

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

Working with IT consultants is an important part of the job and can be one of the more challenging things to manage. Consultants bring niche expertise to help you deploy specialized systems, and when everything works right, it’s a great partnership. But you have to be careful. When things go wrong, some consultants will try to push the blame off on you by arguing that their solution works great everywhere else so it must be a problem with the local IT infrastructure. Conversely, when a project is wildly successful, there are consultants who will try to take all of the credit and ignore the substantial work you did to customize and implement the solution for your company.

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

One of the most attractive things about working in IT is the idea that we’ll get to play with the latest cutting edge technologies. However, that’s not usually the case in most IT jobs. The truth is that IT professionals typically spend far more time maintaining, babysitting, and nursing established technologies than implementing new ones. Even IT consultants, who work with more of the latest and greatest technologies, still tend to work primarily with established, proven solutions rather than the real cutting edge stuff.

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

A lot of companies could implement more cutting edge stuff than they do. There are plenty of times when upgrading or replacing software or infrastructure can potentially save money and/or increase productivity and profitability. However, it’s often the case that one of the largest roadblocks to migrating to new technologies is not budget constraints or management objections; it’s the veteran techies in the IT department. Once they have something up and running, they are reluctant to change it. This can be a good thing because their jobs depend on keeping the infrastructure stable, but they also use that as an excuse to not spend the time to learn new things or stretch themselves in new directions. They get lazy, complacent, and self-satisfied.

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

Another subtle but blameworthy thing that some IT professionals do is select and implement technologies based on how well those technologies make the business dependent on the IT pros to run them, rather than which ones are truly best for the business itself. For example, IT pros might select a solution that requires specialized skills to maintain instead of a more turnkey solution. Or an IT manager might have more of a Linux/UNIX background and so chooses a Linux-based solution over a Windows solution, even though the Windows solution is a better business decision (or, vice versa, a Windows admin might bypass a Linux-based appliance, for example). There are often excuses and justifications given for this type of behavior, but most of them are disingenuous.

1.) IT pros frequently use jargon to confuse nontechnical business managers and hide the fact that they screwed up

All IT pros — even the very best — screw things up once in a while. This is a profession where a lot is at stake and the systems that are being managed are complex and often difficult to integrate. However, not all IT pros are good at admitting when they make a mistake. Many of them take advantage of the fact that business managers (and even some high-level technical managers) don’t have a good understanding of technology, and so the techies will use jargon to confuse them (and cover up the truth) when explaining why a problem or an outage occurred. For example, to tell a business manager why a financial application went down for three hours, the techie might say, “We had a blue screen of death on the SQL Server that runs that app. Damn Microsoft!” What the techie would fail to mention was that the BSOD was caused by a driver update he applied to the server without first testing it on a staging machine.

This article was originally published on TechRepublic.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Jason Hiner is the Editor in Chief of TechRepublic. He writes about the products, people, and ideas that are revolutionizing business with technology.

Disclosure

Jason Hiner

Jason Hiner has nothing to disclose. He doesn't hold investments in the technology companies he covers.

Biography

Jason Hiner

Jason Hiner is the Editor in Chief of TechRepublic, an online trade publication and peer-to-peer community for IT leaders. He is an award-winning journalist who examines the latest trends and asks the big questions about the technology industry. He previously worked as an IT manager in the health care industry.

You can also find him on Twitter, , Facebook, and at JasonHiner.com.

113
Comments

Join the conversation!

Just In

RE: 10 dirty little secrets you should know about working in IT
arcxjo 19th Jul
I don't work in IT, and yet I've seen every one of these -- with the exception of #10, which exists in every other industry just without the "pay you well" part.
0 Votes
+ -
Interesting Bias
curph 13th Dec 2010
Its interesting that the least important things (10 -4) are pro IT personnel or at least neutral while the most important items (3 -1) are decidedly anti-IT personnel.
@curph

You obviously don't read much Kingsley-Hughes. If you did, you'd know if you look up 'biased' in the dictionary, his picture is the disambiguation.
0 Votes
+ -
@Curph
SonofaSailor 13th Dec 2010
...but all true none the less.

I've run into every example listed. The only thing I would add is on #1; yes, some will use jargon to hide their mistakes (or their lack of knowledge), but some guys talk that talk because they can't or don't know how to express the issue differently. Lack of communication sometimes is for alterior motives, sometimes because the tech doesn't know any better.
0 Votes
+ -
@SonofaSailor The only thing I would add is on #1; yes, some will use jargon to hide their mistakes (or their lack of knowledge)....

Funny thing is, it seems implied that only I.T. does this. I find myself trying to remember any profession that didn't.
@Badgered agreed, every profession from politicians to janitorial staff spins the truth to cover their mistakes.
0 Votes
+ -
I was thinking the same thing, Badgered
arthurborges@... Updated - 13th Dec 2010
I'm teaching at a government university in China and I'm helping recruit new teachers right now. I can do that because I have no fear my bosses will oust me. For starters, they (1) keep their word, (2) wine & dine us every now and then to make us feel appreciated and (3) treat everyone with an even hand (the acid test is when management treats the occasional total jerk just like those who do their job satisfactorily and submit paperwork on time).

Maybe if management invests a little more in ego-stroking and nurturing its people, it will have _less_ of a problem with individuals consolidating powerbases?
@SonofaSailor
yeah but #2 the way its phrased is stupid. You mind as well say "some" IT worker goes into their office and shoot up the place. What does "some" equate in his research, 1 out of 10, 1 out of 10,000, that one time when there was an incident with that IT dude who just came out of college and so that one incident is now "some".

As for #3, my experience has always been the end users who are the road blocks because they don't want to pay for it. Usually the technology is too new so they don't understand it. Its not on their ipod so they can't relate and they don't want to try it.
@rengek

I completely agree with you about item #2. I like this list a lot... very realistic overall. But item 2 kind of bothered me, because I don't really find it's the case very often. I've been working in I.T. for about 20 years now, and I'd say most of the time, it's simply a matter of individuals not having the time or capability of becoming an expert in all areas. If, for example, you put in loads of hours learning Oracle databases, you're going to push for an Oracle DB solution when a database server is implemented. Other I.T. hires who aren't familiar with Oracle might be quick to assume it was done simply as "job security" for the guy who made that decision. But that's a cynical outlook that's probably not really accurate. It's much more a case of someone trying to use a solution they're really familiar with and know is capable of getting the job done, vs. going with a possibly cheaper alternative they don't really know the limitations of.
0 Votes
+ -
Replace some with most
Bruizer 13th Dec 2010
@rengek

IT is all about consolidation of their power with little concern to the business units they serve.
0 Votes
+ -
@SonofaSailor " Lack of communication sometimes is for alterior motives, sometimes because the tech doesn't know any better" -- OR, the user/management does not know better!
@SonofaSailor

I wouldn't exactly call them secrets, in most cases they are all expected by upper management. However, don?t be dissuaded, I spent 20 years in IT. I have won some and lost some. I have made many supporters and many enemies and in the end I believe that I was an asset to the company. I would highly recommend a job in IT for anyone who loves to work with technology, people and has the courage to fight for what they believe. And yes I am one of those old techies? RonR
@SonofaSailor Or some techs just simply lack the social eptitude to speak on other people's levels. I have been in the middle of this for most of my career, I can put things in normal people's terms where many high level engineers don't ever even think on that level.
0 Votes
+ -
Good List ...
Ludovit 13th Dec 2010
... but it really could go on ...

Ludo
@Ludovit

... and on and on and on...

i've especially encountered # 10 and # 7
#4 You?ll spend far more time babysitting old technologies than implementing new ones

As our I.T. department is under accounting... I think I know why this is.
0 Votes
+ -
Me too.
John Zern 13th Dec 2010
I answer to the VP of finance. it seems like we can "never afford all of it, so lets go with just..."
wink
0 Votes
+ -
And how did that work out?
daftkey 13th Dec 2010
@John Zern -

And with that compromise in mind, did the VP Finance, the CEO, and everyone else that the system was meant to serve receive the benefits that they expected from the system?
@John Zern
That may just explain why you have become such a pro-MS zealot. They've never bothered to properly look at a better solution, because it may appear more expensive, or is just unknown.
@John Zern

normally that extra bit you asked for but didn't get went into their pockets as a bonus for not spending it on IT... The worst is the guy who won't allow you to implement a system or new technology that will simplify your workload.

current example at my job...
we use Citrix 4.5 on most of our citrix servers, we have some x64 win 2k3 servers, the rest are 32-bit and maybe a half dozen or so 2k8 machines all x64 but most not running citrix, there is a known issue with 2k3 x64 and citrix 4.5 that was fixed in citrix 5.5 and up. But they won't update citrix. meanwhile hundreds of incidents occur each month that could be resolved by upgrading the current citrix infrastructure, nothing else needs to be done, just update the software. Doesn't even have to be the newest version, 6.x... but it isn't going to happen, instead they approved a project to update the print servers to windows 7 compatible print drivers (read HP and Canon universal print drivers, also not the newest versions...), did I mention there is not yet one windows 7 computer on the network?
0 Votes
+ -
1- I find it better to admit an error was made, that it has been resolved and what measures have been take to divert it from happening again. We are human and things will happen. You don't stop learning just because your out of school, that will continue for the rest of your career.

2- Very true, I've seen it personally with the programmers especially... but your doing a dis-service to the business your supporting... you must think out of the box and be three steps ahead.

3- Veterans can be an obstacle, most are just afraid of losing their jobs because they are no longer taking the time to expand their knowledge and skills.

4- Very true. Most companies cannot afford the newest technologies and just use what works for them. It's a slow process upgrading but you just have to do your research and present it in a business mindset.

5- This is the way of the world. Just know your infrastructure and do the R&D.

6- Oh YEAH! They come to you for everything, thinking because you work with them they can get free tech support. I always tell them, nothing is for free and give them my contract rates. If they don't like it, they can go elsewhere which I prefer they do anyway.

7- Certifications are a great way to get doors to open but don't think that it has any weight with veterans, it just means you can pass a test, you have NO real experience. Once you've been in the field for a while, you'll learn that their are many different ways of doing things and that the correct answers on the test are rarely the best or the most efficient use of your time. Ever heard the term "Paper MCSE's"?

8- Way of the business, you will be hero/goat constantly.

9- All the time, we use two special acronyms for these issues.

10- Pay rates really depends on where you live. South Fla is not that great but that is beginning to change. The demand for experienced I.T. professionals is growing.
0 Votes
+ -
re: paper MCSE's, etc.
kingtj 13th Dec 2010
@csonera

The biggest problem I've seen with "certifications" is that usually, they're developed by commercial entities that also sell I.T. software or products. Even concepts you'd think would be universal are often edited so they're biased towards that company's technology. (EG. I remember when Microsoft's training on the basic network layers was different than Novell's.) If you attain advanced certs. provided by only one or two vendors, you tend to think of solutions to problems using only the products/services offered by that same one or two vendors.

When companies say "We're an all Microsoft shop!" and give preference to hires with MCSE's, they really create a self-fulfilling prophecy of ALWAYS remaining an all MS shop, even when it's detrimental to their efficiency or cost-savings.
@kingtj
Very good point. Add to that some marketing tricks from MS and thing move to the MS shop since Linux does not play golf (wink) with the C I O.
@kingtj

Excellent point! With the possible exception of CompTIA, most of the certifications (i.e. Microsoft, Novel, Cisco, etc.) are biased... their certifications are geared to push their products and mindset.
@csonera

regarding #7: the tech vets rarely do the interviews or hiring, that's usually HR, who doesn't know the difference
0 Votes
+ -
RE" certifications
rahbm 13th Dec 2010
@csonera
Industry certs can be significant, particularly if they are vendor independent, eg Comp TIA. However, many vendor certa are almost useless, eg the trainer who had EVERY single MS cert possible, but could not explain (during the interview) the basics of what a router does! I guess they must be unnecessary since MS doesn't make them....

Then there are the Cisco certified people who rubbish anything from any other vendor, regardless of performance, capabilities, or value for money.
@rahbm

Very true, certs can be significant but, as you stated, the problem is that most are vendor dependent. CompTIA certs are the exception to the rule.
@csonera

The biggest issue with Certs now is that there high schools that have MCSE training tracks where you get out of your basic education to take tech classes and graduate high school with an MCSE or even more advanced certs, having never worked for any company ever.
0 Votes
+ -
You Forgot The Most Important
cyberslammer2 13th Dec 2010
Company hiring a CIO who either has zero experience in the field or hasn't worked in technology since Windows 3.1.

I've seen this happen more times than I can count, you get somebody at the top whose sole reason for getting the job was because someone knew someone that knew someone that owed someone a favor, and got them the job.
0 Votes
+ -
@cyberslammer2 good points 100% agree! I.T. is all about keeping it simple, people who are in I.T. and don't undertand the technology like to make things complex so as to hide behind their failings.
@cyberslammer2

yup.
The biggest problem with that group is that they won't keep up with the technology because they are not entrenched in it day after day. So they lose their relevance very quickly when it comes to contributing to innovation. But they can't come out and tell you "I am clueless about this" or "I don't know" because they're the leader. So they'll end up torturing you instead.
@cyberslammer2
Or because they always say what their boss wants to hear. There's a term for them --> YES MAN and I don't mean Jim Carrey.
@cyberslammer2

I've seen it more than I care to discuss. Quite maddening to see someone without as much as a clue on how to search his email sitting in a top dollar position. That contributes to a hostile work environment when the only argument is "...cause I have a title and I say so."
@cyberslammer2 RIGHT ON!!!
@cyberslammer2 Agreed 100%. I've worked for many "VP" level people who either had zero clue about technology or, worse, did some "data processing" or similar role in the 70s and somehow got to be in charge of IT departments. They know nothing, they're unwilling to listen to anyone who knows what they ARE talking about, and toss around their title/position to get their way.
@cyberslammer2

By any chance, are you referring to those members of `damagement` we often deride as "sexual intellects"? (Sorry, had to `keep it clean`.) The simple fact that they have a title and an MBA* degree qualifies them to cause an IT department to `fly into the ground`. To me, the worst type of situation is an IT department head that is straight out of `bean counter` school; with NO practical experience, trying to tell a DBA how to perform data migration.

These are the kind that you wish to experience `elevator shaft` accidents.

* MBA = Manglement By A--holes
@cyberslammer2 Case in point, I applied for the CIO position at a local university, it came down to me and another individual who was already employed at the university. He was selected, although I knew I was way more qualified and had way more experience than he did.

First university-wide faculty meeting he gets up in front of everyone and tells them that it's not a good idea to use IE8 because it's still in beta testing and not in full production...he said this in August 2009...IE8 had been full production since March.

If someone can't even get a simple thing right as to what's beta and what's not, how can you expect them to run an entire university IT system?
0 Votes
+ -
Money, meet mouth?
daftkey 13th Dec 2010
@cyberslammer2

So what makes you more qualified than the person who was already working at the University - other than he didn't know the development plans of a specific web browser. Do you know the University's needs better than this person? Their inner-workings?

If you were hired, what was your IT strategy going to be, and how was it going to benefit the University?
@cyberslammer2
Yes, it is always disheartening to be in that position; the insider usually has the running regardless of skills and experience, because they have the ear of management.

At least this guy had the right idea of not implementing IE8, if for the wrong reasons.
@cyberslammer2

That's the kind of thinking that keeps you in the office behind a keyboard and not out in the business making decisions that affect the company.

Now, it sounds like an oxymoron to have a "Chief Information Officer" on staff who doesn't really know technology all that well, but you have to remember who the CIO reports to and what the CIOs job really is - namely, the CIO's job is to align business with IT. He reports to the CEO.

While it definitely helps the CIO to know what ethernet is, or why it might or might not be a good idea to virtualize xyz server or why Windows 7 might or might not be a good idea for the accounting desktops, that's not his job.

His job is to define the overall strategy for IT, with the emphasis on the needs of the business. You may be surprised at how little thought need be given to specific technologies by the most successful of CIOs in the world today.
@daftkey

to align business with IT, or to align IT with business?
@daftkey Spoken like a future CIO clueless leader.
@erik.soderquist

Touche, my friend. happy

Although, the CIO might well have done his job properly if the difference is subtle enough not to matter.
0 Votes
+ -
Clueless?
daftkey 13th Dec 2010
@cyberslammer2

What part sounded "clueless" to you? The part about the business requirements being more important than the technology, the part about the CIO being more responsible to the business than the technology, or the part about the need for the CIO to define the overall strategy for the IT department, rather than just thinking about routers and operating systems and cabling?

Somehow your single sentence explained more about the reason you missed out on that CIO job at the University then your entire rant above. Bravo for being so succinct.
@daftkey No, your response proves why CIOs continue to be clueless and organizations continue to waste money instead of getting someone in there with real leadership and knowledge instead of hiring someone that kisses corporate butt or is owed a favor.

And just an FYI, the person who beat me out for the position was already selected ahead of time, I'm glad I wasn't selected because I took a position online after that and I'm fortunate enough not to have to wear a three piece suit with puppet strings attached like you probably do. Corporate IT is a joke.
0 Votes
+ -
@cyberslammer2

You still didn't answer my questions on a) What made you better qualified, and b) what part of my response sounded clueless to you?

As for your "online position", Bill Gates handing out his millions for forwarding a few emails wouldn't have anything to do with that, would it?
0 Votes
+ -
Unlike many fields where you study a discipline and then just get better at doing it, much of what you work hard to learn will be completely obsolete in a few years. You will have to constantly learn new technologies just to stay relevant in your position.
0 Votes
+ -
All True (For ME) except #10
bobiroc 13th Dec 2010
But that is because I work in education IT and I get some added benefits that many people do not get out in the corporate world.

Also have to agree with Cyberslammer as my Director of Technology is a complete idiot and can barely turn a computer on let along run an IT department. I also have difficulties with my Network Manager being a control freak.
@bobiroc

lol, I feel that way about network managers as well. Buuut I do cut them a lot of slack. They kind of have to be that way because any kind of security breach is their fault. Nevermind that you tell everyone not to plug in a flash drive and take sensitive work home, they'll still do it. And when someone finds out, the culprit will say "oh if you really didn't want us to do that then you should have made sure my computer couldn't actually have that ability".

But the network managers do need to lighten up some of the ridiculous policies that makes you feel more secure but really does nothing. Its like a TSA airport security measure. It does nothing.
@rengek

Oh the type of control freak I am speaking about involves restricting top level IT Staff like myself from things just so he can be on his own little power trip. I am the systems admin so I mainly deal with the end point devices and a few related servers. I do quite a bit more but that is what my job role is. Really I do everything from changing toner to network security. My network admin really does not do his job well IMO and hires out for consultants and vendors to do much of what he gets paid $30,000 more a year than I do. I do more network fixing than he does but he gets all the credit. Anyway you don't need to hear the personal roadblocks I have I just wanted to clarify that the controlling aspect is not the good kind of control. Believe me I am the first to say security over convenience but he is like a dictator even with the IT staff that needs access to do their job. Especially when he goes on vacation. I think that is why he does it so it makes him look like he is absolutely needed to cover his own incompetence.
My personal favorite are the non technical managers who have read a few articles or maybe took some basic programming in college so they'll tell you "i can roll up my sleeve and help you guys if necessary". Because those folks are always trying to drive the direction of IT in the most asinine ways.
I don't work in IT, and yet I've seen every one of these -- with the exception of #10, which exists in every other industry just without the "pay you well" part.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix