3 ms·

Getting around the policies just to get around the policies makes you an ass, I agree. Getting around the policies to do your job, on the other hand, does not.

Getting around the policies just to get around the policies makes you an ass, I agree. Getting around the policies to do your job, on the other hand, does not. I worked at a firm where I was asked by a VP to perform some testing on a VM. The VP wanted the test results by the end of the week. IT said that it would take at least three weeks to approve the specific VM software for my machine, even though there were other developers already using the software. End result? I ended up installing it and doing my job without IT's permission. I had made sure to get everything in writing from the executive, so I could show IT my reasoning if I was ever called out for it. I'm not proud of what I did, but I don't think I should have to ask permission in order to do my job.

gatlin 15y ago
That's actually very similar to my situation, and I sympathize. I was told verbally that I could use IIS, Access, and Perl (I didn't know it at the time) to whip up my project. And then inexplicably a number of Perl tutorials were flagged by the agency firewall at the time. Also, I tend to read sites like this one in case something useful comes up - and of course, these kinds of sites are blocked. I illicitly installed IIS, Access, and Perl while waiting for approval and the day the guy came in to install I faked some meeting so he'd come back in 20 minutes, uninstalled everything, and then let him install things. But that's not as funny to me as the original telling.