Twenty years ago the most intimidating person in a company was the person with the key to the stationery cupboard. They’d query why you wanted two pens instead of one, complain about how quickly you were going through your notebooks (as if documenting less would be better) and positively sniffed at you if you needed … Continue reading “IT Bullies”
Twenty years ago the most intimidating person in a company was the person with the key to the stationery cupboard. They’d query why you wanted two pens instead of one, complain about how quickly you were going through your notebooks (as if documenting less would be better) and positively sniffed at you if you needed pens and notebooks at the same time especially if you were a new start.
The grumpy sod in charge of the stationery has been replaced with the IT Bully. They still hold the keys to productivity but they actively attempt to stymie you, or so it would seem.
They don’t enable
The more functionality you have, the more the IT Bully has to manage. This can be simple (like preventing the user from changing his desktop background) to complex (hiding the Connections tab in Internet Options so not only can you not change the proxy setting but you can’t even view them – should you need to, for example, attach to a different network or try and get a machine working on your current network) to inane (setting up all of the machines on the LAN to talk to a Time Server in order to keep the clocks in sync – but that clock is not only 10 minutes fast, you’re also blocked from changing it manually).
They don’t care about your work
It’s not their work. Their world is all wrapped up in WINS, Active Directory, Forests, DOMAINS, Policies and Profiles. The ports they use are tied up in Windows-specific services, MAPI, their own monitoring ports. They don’t consider that you may need to access services in high order ports, use IMAP/POP3 services outside the LAN, connect using SSH/SFTP or any number of other possibilities.
For example, changing the firewall and proxy settings over the weekend and not telling the client which means that anything they have added to the network stops working on Monday morning. The event which inspires this rant involved exactly that – a forced change which we were not informed about, when queried, was initially denied and then responded to with aggressive language designed to intimidate.
They exploit fear, uncertainty and doubt
This serves to intimidate the non-technical using language like “I’m sure you can all appreciate the importance to retain the highest level of security feasible…” or “I’m sure you understand the need to maintain the need for review of security on the ICT systems and the importance of authorisation to open service ports to the Internet” while stripping us of essential services or denying us products and services which might actually make our job easier. Sadly things haven’t changed – they don’t like it if you want to use a Mac or if you want to use an Smartphone or PDA with the system. They’re not keen on new software, on web-based services which bypass their provisions and claim ignorance if you ask for the settings which would enable you to sort things out yourself.
When cornered, they attack.
Another memorable IT Bully was Justin. He talked the talk but never quite managed to walk the walk. He claimed knowledge of UNIX and network that he could never demonstrate and had to be guided through even the simplest processes but he was in charge of the Windows IT network on site. For nine months he ‘evaluated’ a top spec laptop running the latest Windows build yet in the end it had to come down to the other members of his team to deliver the promises he made – and even then the build was lacking multimedia (promised), PCMCIA support (essential), Sleep/Suspend support (obvious for laptops) and support for additional monitors, IrDA, modems or wireless. When confronted at a project meeting with the problems, his response to me was “Shut up, Macboy” which thankfully ended his participation in any of the important projects that we had to manage.