Slashdot Mirror


Beck and Andres on Extreme Programming

narramissic writes "In recent years, Extreme Programming (XP) has come of age. Its principles of transparency, trust and accountability represent a change of context that is good not only for software development but for everyone involved in the process. In this interview, Kent Beck and Cynthia Andres, co-authors of 'Extreme Programming Explained: Embrace Change,' discuss how XP makes improvement possible."

6 of 321 comments (clear)

  1. Extreme... by celardore · · Score: 4, Funny

    I was hoping for something a little closer to Extreme Ironing.

    That would have been cool.

  2. Laundry? by LaughingCoder · · Score: 3, Funny
    FTA:
    I think that the first book was in reaction to a culture for programmers that was basically camping in their cubicles in Silicon Valley where people were spending their entire lives living out of cubicles with food brought in and laundry taken out.
    There are places where they take out laundry? Real programmers don't change their clothes until the job's done!
    --
    The more you regulate a company, the worse its products become.
  3. Why is it called "Extreme"? by 10Ghz · · Score: 4, Funny

    To me, the word "extreme" sounds like they program in assembly 24x7 for one week straight, or they program with laptops, while running away from a pack of wolves or something. But apparently it's not like that. So what makes it so "extreme"? Did they come up with that name when they were discussing their interests with their jock-friends?

    "Oh yeah, I'm in to pretty extreme things. Currently I'm doing base-jumping and ultimate-fighting. How about you?"
    "Well.... uh.... I'm in to.... EXTREME programming"
    "Whoa! Radical!"

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    1. Re:Why is it called "Extreme"? by Anonymous+Codger · · Score: 4, Funny

      It's called Extreme because they take some basically good ideas and push them to such extremes as to be completely useless in the real world.

      --
      No sig? Sigh...
  4. Real Extreme Programming by niceone · · Score: 5, Funny

    IMO real extreme programming should involve at least 3 of the following:

    1. Only having 24 hours to deliver the code
    2. Failing would cause thousands of innocent people to die
    3. Getting your interface specs from a dieing man after being helicoptered across town
    4. Using emacs
    5. Failing code review results in you and/or your spouse being shot in the leg
  5. Re:Overrated by sammy+baby · · Score: 3, Funny
    Your post reads like a summary of the book, "Extreme Programming Refactored: The Case Against XP," by Stephens and Rosenberg I recommend it for everyone, including people who are using XP successfully.

    If nothing else, it's worth it just for the song lyrics:

    Eight Builds a Week

    (Sing to the tune of "Eight Days a Week" by The Beatles)

    Livin' in a timebox
    Guess you know it's rough
    Gotta build every day, babe
    Even half-baked stuff

    Build it, ship it
    Build it, ship it

    Ain't got time for design, babe
    Eight builds a week

    Build it every day, babe
    Build it right on time
    One thing I can say, babe
    No time for design

    Refactor it, test it
    Build it, ship it
    Ain't got time for design, babe
    Eight builds a week