kevaburg (3/20/2013)
My train of thought is that although from my side it is far more work and attention to detail, I can reduce the amount of damage that a single developer (that incidentally still insist on developing on production databases) can do to the entire instance.
If I had a developer who insisted on using production for development, my management would get an ultimatum - him or me, with an explanation of the hazards associated with developer access to production. Doing development on a production database is stupid to the extreme, and possibly illegal if your company is subject to US SOX regulations. I can't think of a reason to ever allow a developer anything other than read access to production data.