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

Posted by Cliff on Friday October 26, 2001 @06:52AM from the coding-under-lock-and-key dept.

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?

1 of 648 comments (clear)

Re:Trust? by scoove · 2001-10-26 07:25 · Score: 5, Funny

It is rather amusing, not trusting developers. By definition (apologies for being redundant), but developers do not work in a static environment.

Having been in both ends of the pool, it never fails to amaze me at all the rules the corporate "golds" make up, then act surprised when development objectives get missed.

I'd suggest a copy of Yourden's "Death March Projects" be left on the culprit gold's desk for their inspection. It won't work, but it'll be worth a few good stories.

*scoove*