Slashdot Mirror


Should Developers Have Access To Production?

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."

9 of 402 comments (clear)

  1. Re:For me by stillpixel · · Score: 5, Funny

    User: There is an error on page X
    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.

  2. überdev by Anonymous Coward · · 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.

  3. Re:As a developer: read-only access by EricWright · · Score: 2, Funny

    You gotta know how to talk to admins. Tell them they also can be replaced by a very small shell script.

  4. Re:What a silly question. by John+Hasler · · Score: 5, Funny

    > There's a difference?

    Sure. The monkey is trained.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  5. Re:What a silly question. by vegiVamp · · Score: 5, Funny

    As a systems admin, I can assure you that there is definitely a difference.

    Trained monkeys get free bananas and are allowed to fondle their bits in public, to name but two.

    --
    What a depressingly stupid machine.
  6. Re:For me by characterZer0 · · Score: 2, Funny

    Unfortunately, copying prod to test does not copy the users, which are often an integral part of the error.

    --
    Go green: turn off your refrigerator.
  7. Re:For me by es330td · · Score: 2, Funny

    I did this once and hosed a production Informix system. We had over 100 external users call in before it was realized and fixed. Fortunately, I did it because my manager told me to so I kept my job and she was reprimanded for A) changing production and B) asking someone else to do it and not doing it herself. I learned my lesson and in the subsequent 10 years have never modified a production system without thorough dev testing first.

  8. And the winner is ... by galego · · Score: 3, Funny

    ... in a split decision, vi wins. Oh wait ... wrong holy war!

    --

    Que Deus te de em dobro o que me desejas

    [May God give you double that which you wish for me]

  9. I think I speak for all programmers when I say by geekoid · · Score: 2, Funny

    No. Do not give developers access to the production machine ever, except me...just this once..

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect