Comment Re:I used to work in IT and.... (Score 4, Interesting) 960
No in my experiences it is IT's insistence on security practices with zero thought on how this will impact the end user. A few examples:
I was looking after a Jenkins server for a project we were running, Jenkins was running on the latest version of Tomcat with a Java 6 runtime. However due to customer requirements there was also a Java 5 runtime which as being used to generate the build. IT felt the need to un-install the JDK 5 and upgrade the the machine's Java 6 (to the version with Oracle in its name). The removal didn't update the Java_Home directory causing Tomcat not to work. They decided to do this just as we were starting an Integration & Test phase for a major release. The Jenkins server was linked to me on their records but at no point did they think to mention it to me.
Same Jenkins server, this was running fine and suddenly the builds starting failing. 3 hours of investigation later I find out its because the Jenkins server password has been changed. Never mind the server username was the name of the project (e.g. projectXYZ). IT came up with a new policy which stated all server accounts needed to be > 48 characters and they had changed them all without notifying a single person on the project.
How about when IT decided that in a software house no one needed Admin access, which would be fine except they tried to forbid admin access on projects which were developing software which required Admin access (for a number of reasons). Those projects had to go up to the business director and have him shout at the IT head to fix it.
Or the fact they decided no one should have USB. A great idea except I was working on an embedded project (along with a dozen other projects) which required an unencrypted usb stick to load the software on to the test rig. Once they realised how many people had a problem they tried to limit it. But when your working on a 5 man team only allowing 1 person to transfer files causes you to loose a lot of man hours.
I can think of dozens of other examples, none of them were dictated by upper management. People hate IT because IT doesn't look at how to better help people work.
I was looking after a Jenkins server for a project we were running, Jenkins was running on the latest version of Tomcat with a Java 6 runtime. However due to customer requirements there was also a Java 5 runtime which as being used to generate the build. IT felt the need to un-install the JDK 5 and upgrade the the machine's Java 6 (to the version with Oracle in its name). The removal didn't update the Java_Home directory causing Tomcat not to work. They decided to do this just as we were starting an Integration & Test phase for a major release. The Jenkins server was linked to me on their records but at no point did they think to mention it to me.
Same Jenkins server, this was running fine and suddenly the builds starting failing. 3 hours of investigation later I find out its because the Jenkins server password has been changed. Never mind the server username was the name of the project (e.g. projectXYZ). IT came up with a new policy which stated all server accounts needed to be > 48 characters and they had changed them all without notifying a single person on the project.
How about when IT decided that in a software house no one needed Admin access, which would be fine except they tried to forbid admin access on projects which were developing software which required Admin access (for a number of reasons). Those projects had to go up to the business director and have him shout at the IT head to fix it.
Or the fact they decided no one should have USB. A great idea except I was working on an embedded project (along with a dozen other projects) which required an unencrypted usb stick to load the software on to the test rig. Once they realised how many people had a problem they tried to limit it. But when your working on a 5 man team only allowing 1 person to transfer files causes you to loose a lot of man hours.
I can think of dozens of other examples, none of them were dictated by upper management. People hate IT because IT doesn't look at how to better help people work.