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?

Re:Trust?

[scoove]

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*

Re:How To Reduce Productivity 101

[PollMastah]

however, saying that programming is is a highly creative process, and human creative processes are very easily hampered by frustration, irritation, and disillusionment is just bull. It may be irritating, but it's your job and you have to do it well or you should leave. there are commercial artists. they don't love creating mcdonald's billboards. they might go home and paint frescos to satiate their creative urges. but they do their damn work because they are paid to, and programmer shouldn't be held to different standards.

No, you're missing my point. Actually I agree with you that programmers shouldn't whine about their job; if they don't like the job, go find something else. If they can't then they'd best shut up and put up. But my point is that, from the POV of an IT manager, making the programmers under you suffer like this is bad management. Your programmers won't perform well, and they will just be bitter and hard to manage. I'm not saying that programmers are right to be bitter; but if you're a manager and you cause them to be bitter by imposing unnecessary red tape on them, then don't be surprised they write a lousy product for you. And from a management point of view, this is a stupid route to take. That's all I'm trying to say.