Can Developers Work in a 'Locked-Down' Environment?

brad-d queries: "My company is seriously considering enforcing a SOE on all employee computers, including developers. The level of lock-down would likely include baring the Windows registry from changes (and in effect stopping the installation of new software). The goals of this SOE are to prevent users from installing unlicensed software, plus some support issues. What are others experiences with situations like this? Can a developer really work in a lock-down environment? What compromises could be made between developers and IT services? And no, Linux would be likely banned." It depends on how "locked-down" said environment is, and what the developer would be will be working on, however if the Registry is locked with no mechanism provided for the Developer to add in whatever keys are necessary, how much real developing can one do?

Comments

Re:No, you can't.

[Anonymous Coward]

Having prima donna devs is not the problem. It's the software. If any software needs access to the Registry, then the dev is SOL. Also, when developing shrink-wrapped software Setup programs require Registry access, you wouldn't want to lock out the Setup team.

Having a set of tools that everyone must use is not a bad idea, but locking down the Registry is a terrible idea.

Re:Yes, but at a much slower rate...

[atrowe]

Let me get this straight here: The guy is developing Windows applications, and specifically said that he is not permitted to install other OS's, and your suggestion is for him to run Linux. You rode the short bus to school, didn't you?

Re:Locking down is necessary

[WasterDave]

Another vote for 'good troll'. And increased calls for a slashdot troll archive, for these truly are the art on slashdot.

Dave