Should Developers Have Access To Production? 402
WHiTe VaMPiRe writes "Kyle Brandt recently wrote an editorial exploring the implications of providing developers access to the production servers of a Web site. He explores the risk introduced by providing higher level access as well as potential compromise solutions."
Re:For me (Score:5, Funny)
I tweak that page code on the production server after looking at the error log. Me back to User: An error really? Have you tried pressing F5?
User: Oh.. hmmm I guess I must have done something wrong. Sorry for bugging you!
Me: Hey, no problem.
überdev (Score:3, Funny)
I am one of the few people who can run correct code the first time round. I am also proficient enough in OS matters to be able to circumvent access to locked down resources. So I don't care what this post says, I'm doing it myyyyy waaaaay.
Re:As a developer: read-only access (Score:3, Funny)
You gotta know how to talk to admins. Tell them they also can be replaced by a very small shell script.
Re:What a silly question. (Score:5, Funny)
> There's a difference?
Sure. The monkey is trained.
Re:What a silly question. (Score:5, Funny)
Trained monkeys get free bananas and are allowed to fondle their bits in public, to name but two.
Re:For me (Score:3, Funny)
Unfortunately, copying prod to test does not copy the users, which are often an integral part of the error.
Re:For me (Score:3, Funny)
And the winner is ... (Score:4, Funny)
I think I speak for all programmers when I say (Score:3, Funny)
No. Do not give developers access to the production machine ever, except me...just this once..