{"id":246,"date":"2011-11-23T19:27:14","date_gmt":"2011-11-23T19:27:14","guid":{"rendered":"http:\/\/microsoftgeek.com\/?p=246"},"modified":"2011-11-23T19:27:14","modified_gmt":"2011-11-23T19:27:14","slug":"10-drawbacks-to-working-in-it","status":"publish","type":"post","link":"https:\/\/microsoftgeek.com\/?p=246","title":{"rendered":"10 drawbacks to working in IT"},"content":{"rendered":"
\n
\n
By Brien Posey<\/a><\/div>\n
November 22, 2011, 1:21 PM PST<\/div>\n<\/div>\n

Takeaway: People who are trying to break into IT don\u2019t always know what they\u2019re getting into. This list paints a realistic picture of what may lie ahead.<\/p>\n

Like most IT pros I know, I occasionally have friends or family ask me to get them a job in IT. For some reason, a lot of the people who ask me this have a perception that everyone who works in IT is a millionaire or a billionaire. Aside from having an incorrect perception about IT salaries, few people outside IT seem to understand just how tough working in IT really is.<\/p>\n

I realize that TechRepublic is frequented by IT pros, so you probably know all too well that there are both advantages and disadvantages to the job. My reason for writing this article is to give you something you can send to your friends the next time that they approach you with unrealistic expectations of working in IT.<\/p>\n

1: The hours are long<\/h2>\n

There are all sorts of IT jobs, but most of them have one thing in common: They involve working long hours. If you want to work in IT, you better be prepared to work nights and weekends.<\/p>\n

2: Your personal time will be interrupted<\/h2>\n

If you handle a critical support role within your organization, you will likely be tied to a cell phone. And that means you could be called upon to deal with an emergency at any given time. When I first started dating my wife, we were watching a movie at about two o\u2019clock in the morning on a Friday night when I got called to deal with a system problem. Thankfully, she was a lot more understanding than some of the other women I had dated. I also once got a call in the middle of Christmas dinner. Working in IT can be almost like being a firefighter or a paramedic, in that you never know when an emergency will occur and you\u2019ll have to drop everything you\u2019re doing to deal with it.<\/p>\n

3: You have to deal with a lot of angry people<\/h2>\n

One of the worst things about working in IT (especially for helpdesk roles) is that you encounter a lot of angry people. Almost everyone who calls you is upset because they have a problem and they expect you to fix it right now. Often, there is a great deal of hostility behind these calls. Those who are calling are under pressure to get a job done \u2014 and the problem your system caused is preventing them from doing it.<\/p>\n

4: Work tends to be deadline driven<\/h2>\n

Most IT jobs are deadline driven. For example, developers are under constant pressure to deliver code on time. Likewise, network administrators may be called upon to create user accounts or deploy and test new systems by a certain date. Oftentimes, the deadline is completely unreasonable for the amount of work that is involved in the task, but you are expected to meet the deadline anyway.<\/p>\n

5: People expect you to fix their home computers<\/h2>\n

Another thing you are almost certain to run into is that your coworkers will expect you to fix problems with their personal electronics. Don\u2019t get me wrong \u2014 I try to help as many people as I can. However, sometimes, you may simply be too busy to help somebody or they may not understand the implications of what they\u2019re asking. For example, I once had a user approach me about upgrading his Tandy 1000 (which was manufactured in 1988) so that it could run Windows XP. Oh yeah, and he wanted to keep the budget for the project under $200.<\/p>\n

6: People lie to you all the time<\/h2>\n

When I first started working in IT, I had a pretty good idea what I was getting myself into. One thing that really surprised me, however, was how many people lie to you on a daily basis. I found out quickly that end users constantly lie about the nature of the problems they are having. After all, nobody wants to get in trouble, so end users try to cover up self-inflicted problems.<\/p>\n

You can also expect to be lied to by vendors\u2019 technical support departments. I have lost count of the number of support technicians over the years who have told me that a problem is not related to their software, but rather to the computer\u2019s hardware or to the operating system. And of course I won\u2019t even begin to talk about the number of vendors who have lied to me in an effort to make a sale.<\/p>\n

7: You have to keep your education current<\/h2>\n

The IT industry is constantly evolving. IT pros have to learn a tremendous amount of information so they can do their jobs, and that information becomes outdated quickly. The only way to keep your knowledge relevant is to make sure that you keep your education current.<\/p>\n

This can be surprisingly difficult to do. Never mind all the complicated technical material you have to learn. The things that most often stand in the way of keeping your education current are the long hours you are already working and the ever-shrinking IT training budgets.<\/p>\n

8: Things don\u2019t always work the way they\u2019re supposed to<\/h2>\n

Earlier, I mentioned that projects can be deadline driven and that the deadlines tend to be unreasonable. Believe me when I say that there is nothing worse than trying to complete a project by the deadline you have been given only to have things come to a grinding halt as a result of technical problems.<\/p>\n

Computer systems are complicated, and sometimes in spite of your best efforts things just do not work the way they\u2019re supposed to. Something as simple as an inconsistent chip version on a series of system boards can derail an entire project. Naturally, it\u2019s up to you to find the problem and fix it.<\/p>\n

9: You may have to deal with a lot of bureaucracy<\/h2>\n

In the 20 years or so I have worked in IT, there has always been a certain amount of office politics and corporate bureaucracy to deal with. Of course, that is the case with most jobs. However, in the last several years, the bureaucracy has been taken to a whole new level. Corporate scandals such as the Enron incident have led to IT professionals being forced to comply with numerous federal regulations. These regulations almost always make IT projects more difficult, time consuming, and expensive.<\/p>\n

10: Your job is to make yourself obsolete<\/h2>\n

When I first started working as a network administrator, a longtime friend told me something I will never forget. He said that my job was to make myself obsolete. I didn\u2019t really understand what he meant at the time, but he was absolutely right. An IT pro\u2019s job is to make everything work perfectly. However, if everything did work perfectly, IT pros would not be needed.<\/p>\n

Over the years, I have had plenty of people tell me that as long as you work in IT, you never have to worry about being out of work. However, some of the latest generation of management products make it practical for small numbers of people to manage huge numbers of systems. Likewise, a lot of IT positions are going away as systems are being outsourced to the cloud. Even though the IT industry itself probably isn\u2019t going away anytime soon, having IT knowledge is by no means a guarantee of employment.<\/p>\n

Additional reading<\/h2>\n