Well, I've been on both sides of this fence, running networks and client workstations and as a developer. I've seen reasonable arguments from both sides of this issue here.
I think we can probably agree on a few things:
Developing in a locked-down environment *can* be done, but it sucks.
Supporting developers generally sucks for IT
Developers will agree that IT technicians are a sub-class of human being that don't understand the kind of complex realities that developers deal with on a daily basis.
Technicians will agree that there's no faster way to screw up a computer than to give it to a developer.
The people who have made this decision (or generally any business decision made by [insert your company name here]) are not qualified to make it.
The possiblity of IT and Development departments seeing eye-to-eye on this and working out a reasonable solution requires solid and constant communication and coordination (including management listening to the people doing the actual work).
Without the aforementioned communication and coordination, a good solution is about as likely as putting a hundred monkeys in a room with typewriters and getting the bible as a result.
You can now be arrested for having a taillight out or not wearing your seatbelt.
We do imprison millions
The War on Drugs is two decades old and going strong.
Does that refute all your points? I think so.
Slashdot Mirror
Someone needs to compensate me for listening to that preview!
Well, I've been on both sides of this fence, running networks and client workstations and as a developer. I've seen reasonable arguments from both sides of this issue here.
I think we can probably agree on a few things:
You can now be arrested for having a taillight out or not wearing your seatbelt. We do imprison millions The War on Drugs is two decades old and going strong. Does that refute all your points? I think so.