Comment Re:Depressing landscape. (Score 1) 605
Many people on this thread claim that they can't do their job without admin rights of some kind, which is patently untrue
Yet each one of your "solutions" has the obvious effect of stopping me from doing my job. My time is too valuable to the company to have me waiting for a sysadmin, authorization from higher-ups or jumping through bureaucratic hurdles every time a trivial task like installing or upgrading an application/library/whatever has to be performed.
Of course I have local admin rights on my workstation. It's trivial to re-image should I mess it up (hasn't happened yet, mind) and it lets me do my job as efficiently as possible. Of course, since I'm a professional, I don't abuse my admin rights to do anything that might be a nuisance to anybody else. Not that I could do much with just the admin rights to my own workstation. Saturate the network, perhaps - but then an admin would drop by to give me a slap on the wrist within minutes, as the network is properly monitored.
Did I mention, me and my co-developers also have admin rights on the testing, and production servers? Yes, production. Again this is about empowering professional developers to carry out their jobs as efficiently as possible. What if I should screw up and drop all the tables on the production db, you ask? Well, it's obvious I wouldn't do anything like that intentionally, but otherwise, that's what backups are for. Not that I'd expect to keep my job should I make such a mistake.
Perhaps if you work in a "shop" full of pimply-faced code monkeys who can't be trusted with admin rights to the testing environment, or even the computers on their desks, then lots of policies and nazi sysadmins are quite in order. But perhaps then the real problem is with the recruitment standards. I for one wouldn't want to work in a place were such restrictions were necessary.