Agree completely. But on the flip side: as a developer, I'm not being paid to care about those things, I'm being paid to get my work done. When IT policies make it nigh impossible to do my work, and my choices are 1) spend months trying to cut through red tape, instead of doing my job, just to do things that I'd be able to do if there were no IT department at all in place, or 2) bypass some policies and do the things that actually make money for the company, #2 starts to look damn attractive.
A lot of this depends on the company. I've seen the other side of the fence, and understand that point of view. Even at companies with well-run, reasonable, flexible IT departments, there's always gonna be a few know-it-all clowns that want to bypass IT and do stupid things, because they think they're smarter than they are.
But some IT departments are so rigid and inefficient, so narrow-mindedly set on enforcing policies that only work for general office workers (who can do their work just fine with a very limited number of tools), that working around them is the only practical solution for some employees. If that's not how your IT department is, then I applaud you. But don't assume that everyone who bypasses their IT department's policies is simply "arrogant", "self centered", or "some prissy dev".