Slashdot Mirror


Ask Slashdot: What Are The Lesser-Known Roles Of The IT Department?

chadenright writes: On the same day that I was hired into a new IT position, my new employer also bought a pair of $1,500 conference phones from a third-party vendor, which turned out to be defective; I've spent a chunk of the last two weeks arguing with the vendor. During the process I've learned that, as the IT guy, I'm also the antibody of the corporation and my job is to prevent not just malware and viruses but also junk hardware from entering my business's system. As a software engineer who is new to the IT side of things, I have to ask, what else have you learned about IT?
What fresh hell has this software engineer gotten themselves into? Leave your best answers in the comments. What are the lesser-known roles of the IT department?

23 of 355 comments (clear)

  1. If you thought enterprise IT was just software by bferrell · · Score: 5, Informative

    You may have been living in some sort of fantasy world of siloed functions.

    In a large enough organization, there might be specialists in telecom, desktop hardware and server hardware, but usually IT, in general, is charged with all facets of the IT plant... Workstations, servers, networking hardware and telecom (including switching, carrier interconnect and endpoints like conference phones).

    If what you want is to JUST develop software, you need to be in a different role.

    1. Re:If you thought enterprise IT was just software by Anonymous Coward · · Score: 5, Insightful

      Hell, if it has electricity or moving parts, it seems to be I.T. Yes, you will get helpdesk tickets about the vending machine.

      And since I.T. tends to be the one dept that has actual tools and an understanding of systems, our one seems to end up fixing doors.

    2. Re:If you thought enterprise IT was just software by Kjella · · Score: 5, Insightful

      Since he describes himself as "the IT guy" I think this is very far from the enterprise, probably a jack-of-all-trades position in a small company. Since he switched from software development he probably thought of it as running operations keeping the production servers, clients and the network running, secure and up to date.

      As a software engineer who is new to the IT side of things, I have to ask, what else have you learned about IT?

      I never worked that position but... forget the I in IT. You're now the "tech guy", expect to deal with everything from conference phones, photocopiers, printers, the coffee machine, the vending machine, phones and tablets, basically everything the janitor won't touch. And even then expect to get roped in if the thermostat or window shutters aren't working properly to see if you have any tech tips. If you become a bigger organization you split out the server/client into ops and leave the rest for an infrastructure guy. If you become really big you split out the network from that again and put that into ops too. But until there's somebody else you can point to - and no, they think of you as the most qualified "tech" person - you're stuck with it.

      --
      Live today, because you never know what tomorrow brings
    3. Re: If you thought enterprise IT was just software by dougdonovan · · Score: 5, Interesting

      lol, IT is everything that should work but doesnt which includes...from the help desk at level 1...the light bulbs in every office to the starbucks coffee pot in a vp's office that got unplugged by the janitor that works graves. as soon as the general public walks out of their house, gets into their vehicle to drive to work...their IQ drops to 0. they just expect IT to work but are clueless on how to plug the coffee pot back in.

    4. Re:If you thought enterprise IT was just software by RobinH · · Score: 5, Insightful

      There's some truth in this. In our organization, we get audited for ISO 900x compliance every year, and they have to go through all of our processes and validate that we're following our procedures, etc., but during that audit, if the answer is, "our ERP system does that / enforces that" then the auditor essentially goes, "ok, good" and moves on. The funny thing is that we have a custom-programmed ERP system that we're updating and changing all the time. The auditor certainly never audits our software development process or how we incorporate business processes into the ERP system. Apparently to him it's just "magic." However, people come to me (the ERP programmer) all the time with process problems, and I implement solutions directly in the ERP system to solve those problems, often only with the input of the person doing the job, because in many cases it's just obvious what should be done. I occasionally bring these decisions up to management, but most of the time they just defer to me anyway. So in many ways IT here (or at least the ERP development part) is just a branch of management. I find the whole thing rather silly.

      --
      "I have never let my schooling interfere with my education." - Mark Twain
    5. Re:If you thought enterprise IT was just software by DigiShaman · · Score: 5, Insightful

      Forgive me in advance, as I've told this story before: Back in the mid 90's, I used to work part-time at Kroger (grocery store) as sacker. That job paid minimum wage, but, we got tips for sacking the groceries, carting them off to the parking lot, and unloading them into the back of the vehicle. I don't see that going on anymore, an in many cases, the person working the till does the bagging (customer still puts the bags into his/her own cart). But I digress...

      One day, the janitor was out for a week. I was called out to fill the position in his absence. In fact, just to show how hard of a worker I was, I took extra effort to clean the restrooms and mops the floors more thoroughly. Never did see that guy come back to work. However, I was rewarded via holding the janitor position for the remainder of my employment (which I quit after six months). Why would I stick around?? I worked harder, and made LESS money as it was still minimum wage WITHOUT tips. Yeah, I said to myself "fuck this shit, I'm out of here!".

      So what's the point in telling this story?? That no good deed goes unpunished. If you work in IT, don't be "that guy". Being the eager beaver will get you known as the tech guy who's prompt. That's a bonus, but it will hold you back from further advancement. Trust me, I know how that movie played out too.

      Oh, what's it like to be young, ignorant, and down right foolish. I wish I could go back in time and slap myself several times, HARD!

      --
      Life is not for the lazy.
    6. Re:If you thought enterprise IT was just software by usuallylost · · Score: 4, Informative

      It also varies upon where you are in the company. I am the sole IT person working at small, about 100 people, remote office of a much larger company, about 8,000 people. I am the only person in the building who has tools. I get pretty much anything that breaks even if it isn't technically IT related. A lot of the stuff will eventually get handled by the appropriate departments in the company but I am pretty much always the first responder. In addition to my regular IT work I've fixed doors, the refrigerator, the microwave, a garbage disposal, turned off more than one plumbing fixture that was spraying water, assembled furniture and probably more stuff I've forgotten. If I was working at one of our bigger offices I'd wouldn't do all of that. On the other hand, I'd have to commute to one of our bigger offices so it is a reasonable trade off in my view. Besides this other stuff gives me the occasional change of pace.

    7. Re:If you thought enterprise IT was just software by jon3k · · Score: 4, Insightful

      "you're not allowed to connect hardware to the network without us checking it out first"

      What's unreasonable about that? if you bring in hardware and start using it to perform critical work functions, the business now depends on it working. What happens when it breaks? What happens when you leave? Let alone the security implications. Are you storing sensitive information on that computer? How is it secured? Do you work in a regulated industry? I'm sure you're competent enough to manage device security, but do you think that one, extremely non-technical associate, in say, marketing, capable?

    8. Re:If you thought enterprise IT was just software by apoc.famine · · Score: 4, Interesting

      So if it has anything to do about computers they ask the IT guy even though they are so many different levels you can specialize in.

      Not just computers. Anything with electricity and/or a sensor.
       
      My first job I had a VP who needed a large corner office with lots of windows at the far end of the building. And she needed to be able to walk into it through the emergency exit next to the office, because she couldn't be asked to walk through the whole building. So we were asked to make the security work out so she could have her own private doorway. And we were not allowed to spend any money doing it. End result? We just disabled the alarm and security on that door.
       
      Her second issue was that her big corner office at the far end of the building with lots of windows was too hot in the summer and too cold in the winter. Compounding this, she needed to have her door closed all the time, and sat nearly touching the window. Since she had a thermostat, she constantly adjusted it. Not realizing that it didn't do anything, because it was just there to gather zone temp information. IT would get a request every week or two to fix her thermostat, because her office was uncomfortable. Finally got approval to get the HVAC guys in, and they immediately pointed out that when the building was built, they cheaped out on the HVAC system and it didn't have capacity to cool the square footage of that wing. Given this new information, the VP continued to ask IT to fix her thermostat every few weeks.

      --
      Velociraptor = Distiraptor / Timeraptor
    9. Re:If you thought enterprise IT was just software by dbIII · · Score: 5, Insightful

      "you're not allowed to connect hardware to the network without us checking it out first"

      Somewhere behind rules like that is an idiot who brought in a device like a wireless router that acted as a DHCP server or similar and kicked a pile of people off a network annoying a manager enough to implement such a policy. Sure, expensive hardware rolled out everywhere can protect against that, but a policy of "ask before you plug it in" is a lot cheaper than replacing a lot of stuff just in case of people doing stupid stuff.
      Also some hardware on networks is so fragile that anything sending weird packets to it can take it down (HP and Samsung I'm looking at you).
      You are not that idiot the rule is for but in a large enough org there will be a few.

    10. Re:If you thought enterprise IT was just software by dbIII · · Score: 4, Insightful

      you volunteer to take on this other role and demonstrate your mastery and then you negotiate compensation for it

      For a job on a fixed wage?
      You seem a little bit out of touch so perhaps should not be so critical.

    11. Re:If you thought enterprise IT was just software by Anon-Admin · · Score: 5, Informative

      Having worked in IT for over 30 years and having worked for Fortune 100 companies, I have never see it work this way.

      I have seen C-Level executives come in with a great new idea about how they were going to save the company millions by changing everybody's desktop to BYOD. Thus eliminating the need for the company to buy, maintain, and repair desktop systems. That lasted all of 30 days before security and legal come down on him.

      In today's corporate IT environment we have to meet regulations. They may be something as simple as SOX or as complex as GxP. In those regulatory environments having an open network where everyone can bring in any piece of equipment and plug it is becomes a major problem. As such there are policies in place, there is training, there are physical restrictions, and there are software enforced restrictions.

      I am currently working for a rather large Aerospace company that was recently acquired by another company. The new management seem to have problems understanding that having everyone on one network is an issue. The new company has locations in China, Taiwan, and Korea. The company they bought handles government contracts from everyday items to items that are classified. It is a violation of federal law to have foreign nationals on our network because of the government contracts we have.

      So, from a management point of view I am sure that having everyone able to bring in whatever they want and connect it sounds great. however in the real world IT and IT Security are the ones that have to, not only manage them, but they also work to mitigate the legal risk. Some of the more important jobs in IT, is to protect the company's digital assets. Including understanding the laws, regulations, requirements, and licensing of the products the company uses.

  2. The risk to turn on itself by Anonymous Coward · · Score: 5, Insightful

    I've learned that, as the IT guy, I'm also the antibody of the corporation and my job is to prevent not just malware and viruses but also junk hardware from entering my business's system.

    You know how some people have their immune system turn on themselves.

    Some IT-departments becomes like that.
    Instead of stopping malware and junk hardware they stop everything. It makes their job easier.

    A good IT department tries to figure out what the person they stopped was trying to accomplish and tries to find a secure way of doing that.
    Blocking everything would be like a janitor keeping everyone else out since maintenance gets easier that way.
    While the method works for their immediate task the company cannot survive such measures.

  3. Re:It was you being stupid by hawguy · · Score: 4, Insightful

    What you did was not a "lesser-known role" of IT department, it was doing something completely outside of your job role.

    Your employer should have asked legal department to do the legal work for dealing with defective purchase. If your employer bought an office chair that broke, would you get involved also? How about defective air conditioner? Or a defective TV? Would you get involved because the TV was "internet enabled"?

    If conference phone should be supported by IT, *you* should be the one sourcing and buying it. The IT dept has no input in the purchase, then it has no role when the purchase went bad.

    If the vendor claimed that the internet TV was not working due to a deficiency in the corporate network, then yeah, I'd imagine that IT would be involved in proving that the network was not the problem. Which is likely the same argument that the phone vendor is making. "Your firewall is not allowing SIP transit", or "your ISP connection is too unstable for reliable VOIP calls" or some such excuse. If the phones were completely DOA out of the box, I doubt the vendor would be putting up a fight.

    In any case, if I went to my company's legal department to dispute a small $1500 purchase, they'd put it on the bottom of their pile of work and get around to looking at it in a few years.

  4. Avoiding Shelfware by niks42 · · Score: 4, Interesting

    My role in IT was to stop people buying hardware and software without thinking through how it would be used, how all the bits would integrate together and who would support it. I work in hospitals, and they are the worst so far. Clinical departments think it is a good idea to spend a pile of money on some piece of hardware or software, only to find they either can't use it, it is too complex for their staff to learn, it doesn't fit with anything else, it has a huge dependency on something they didn't buy and so on. Most of it ends up not ever being used - hence shelfware.

  5. Re:IT is a black hole by Anonymous Coward · · Score: 5, Insightful

    Not so wise.

    Imagine running a company without IT. Compete with typewriters, rotary phones, snail mail, and nothing but manual processes.

    IT is the bedrock of every modern business. Without it, you might as well be Amish.

  6. Here's my list of lesser known roles by Qbertino · · Score: 5, Funny

    - maintaining a high-traffic quake 3 arena server on company Hardware without anyone noticing

    - coming up with elaborate and well worded excuses as to why I don't have time to set up and maintain MS Office 365 and it's groupware mess and have them let the intern/media-communications do it (the poor fellows)

    - explaining for the n-th time to the utterly clueless online team and the consultant PMs what the difference between a client and a server is, why versioning is important, that it's not *my* versioning but *our* versioning, why ci is a good idea, why manual ftp and working directly on live is a bad idea

    - stareing, day in and day out with awe and amazement at the ultimate shitfest that is WordPresses application architecture and wondering how we as a human race even got this far ... That's just from the top of my head.

    --
    We suffer more in our imagination than in reality. - Seneca
  7. Re: electricity by Anonymous Coward · · Score: 5, Funny

    Fuses are tricky. Just use a penny and pit the old dude back in. Works great. I work in fire insurance, btw.

  8. You have more weird jobs at smaller companies.... by King_TJ · · Score: 4, Interesting

    I've done I.T. for everything from "running out of a large garage" type businesses to mid size companies with multiple offices.

    I'd have to say the weirdest variety of job expectations were at the smallest places. When you're the only I.T. guy hired full-time at a small business, you're immediately viewed as one of the "smart guys" who surely knows how to do X, Y and Z that people want to do - regardless of if it has much of anything to do with computers.

    The weirdest tasks of all had to be when I applied for a job in the local newspaper for a Macintosh tech for a small start-up business that wanted to refurbish older Macs and PCs to resell in daycare settings and secondarily to the public as "great first computers for small kids". I was unemployed at the time and needed to make the house and car payment, so wasn't being too selective. It turned out, the guy running this business came up with the idea because he already owned a number of daycare centers, as well as other rental property. He was a long time fan of Apple Macs, even though he wasn't that great at using them. (He was your typical older guy who attended those monthly users' group meetings held at the local library and knew just enough to be dangerous.) One of the interesting features of his house was this HUGE multi-bay garage built into the back side of a hill. He put about 6 rows of shelving units in part of it, where he collected up old, obsolete Macs that area schools, the local newspaper and others wanted to get rid of. He'd drive his van out to one of these places every so often with a trailer attached, and bring back 25 to 50 of the machines at a time.

    The rest of this garage was stuffed full with other odds and ends that looked like a scene from one of those "American Pickers" episodes on TV. He had tool and die equipment (as he said he used to work in that field years back), a huge collection of paint cans of various colors (probably whatever was left when his rentals needed repainting), a lot of miscellaneous hardware like chains, bolts, hooks, and several vehicles including an older car with less than 500 miles on it, sitting under a cover.

    Right away, this guy was maddening to work for. He insisted that I punch in and out on this old time clock he had sitting in the back on a desk. It was one of those green metal analog clocks where you had to line up the paper time card just right and press the big steel button on top to stamp your time on it. And as it was as ancient as most other junk in his garage, the clock often stopped -- so you had to make sure it was set right before punching your card. And the time it printed was barely legible either. I was supposed to be refurbishing these old Macs, putting collections of kids' games and learning programs on them, and tagging them with price sheets that told you exactly what the computer's configuration was. In reality, I'd get one or two finished only to find the hard drives were dying and they'd only boot correctly every other time. Then, I had to dig through a collection of used hard drives he kept around to try to find one that worked well enough so it would hold the information in a stable manner. Every so often, he'd come around trying to micro-manage my work and scold me about something or other I should be doing, in his opinion, in order to work faster.

    At some point, he figured out I knew how to do things like update web sites, so he'd regularly pull me away from what I was doing to come up to his office in the main part of the house. There, he'd have me update his daycare center web site or upload photos and edit descriptions of his rental homes, or edit listings on his personal .Mac web page trying to sell some of those nuts, bolts and chains he had around.

    In the winter months, he had this wood burning furnace contraption he built to heat the garage. So I had the task of tending the fire in it and adding logs to it regularly each day.

    Eventually, he decided to try to sell a bunch of these computers at a computer show at an area

  9. Re:IT is a black hole by RevDisk · · Score: 4, Interesting

    Your wise friend isn't very wise.

    Within the past six months? IT saved a hundred million dollar contract because we made an incredibly simple reporting portal. Think web version of Excel. Customer loved it. They did not want random Excel files with literally ten thousand VLOOKUPs every morning, which was the previous 'solution'. IT engineered a last minute audio-visual display for a very high name project. We bought and built something for a fraction the cost of leasing, and ended up using the very nice TVs afterwards to upgrade our conference rooms. We not only saved the company money on replacement, we turned a profit. IT facilitated selling stuff the company used to throw out. More money.

    If your IT department is a financial black hole, either you don't get what they do or their head needs to be fired. They should always be earning their keep.

  10. Re: IT is a black hole by jon3k · · Score: 5, Insightful

    You think that in house IT guy is taking advantage of you? Wait until IBM gets their hands on you.

  11. Re:IT is a black hole by Anon-Admin · · Score: 5, Insightful

    Last time I was told "IT is just a cost center" I looked at the VP and asked where he heard that. When he responded with "Accounting" I pointed out that accounting was a cost center as well, heck even your management position is a cost center. I don't understand what IT being a cost center has to do with anything as everyone not in sales is a cost center.

  12. Shooting nekkid chix by dasgoober · · Score: 4, Informative

    I was the web/IT guy for an adult photography company. This company used to take test poloroids of in-coming models, to shop them around to the publishers, to determine if any of the publishers wanted the model to be featured in a layout. Now comes the advent of the digital camera, which would allow these test shots to be disseminated faster, and with less complications. So, being the IT guy, I'm tasked with working the digital camera, taking pictures of naked women in various poses, which jump-started a sideline business of being a nude (the girls, not me) photographer.
    And fueling a major portion of my sex life.