The life of a software developer can sometimes be a little frustrating. Quite often when I work with development teams I am shocked to find that they don’t have administrative rights to their local workstation or they don’t have the capability of choosing what platform they develop on to best meet the requirements of the project.
I think the secretGeek put it when when he ventured that corporate IT may be a form of emotional abuse. Relating this back to software developers specifically, and introducing an analogy – if developers were butchers, then corporate IT would appear to be some kind of gremlin running around taking the edge off the knives to make the job even harder.
Sometimes I have to laugh though. I was having a conversation last night and one of my co-workers remarked how they were having to use a particular .NET technology because they couldn’t get the servers patched with .NET 3.5 SP1.
Apparently they aren’t allowed to install a patch unless it has been vetted through some internal process. One has to wonder what that process is – and how they ensure that the patch is appropriate for their environment. What if it fixes security issues? What are the risks of not patching?
When faced with idiotic odds, I sometimes think it becomes time to resort to subterfuge to get the job done. How would you recommend my co-worker get this patch installed either by manipulating the wetware or somehow sneaking in the upgrade onto the server? I could think of a couple approaches which might be regarded as hacking😛