use Perl

• Not really (IMHO), at least not for that reason :- (Score:1)

  by Adrian (66)

  This is probably not a terribly original observation on my part, but Extreme Programming is horribly misnamed. I don't view it as particularly extreme: it merely says "follow the good programming practices that you already know about".

  That's quite a big "merely" considering how many people ignore good practices on a daily basis:-)

  I agree that, in hindsight, XP was a terrible name - but only because of the "dangerous" / ad-hoc / bungie-jumping connotations.

  To me the "extreme" was always intended to
  • Re:Not really (IMHO), at least not for that reason (Score:2)

    by Ovid (2709)

    Of the practices unit/acceptance test first, pair programming, collective code ownership, refactoring, YAGNI, etc. all seem related to programming to me :-)

    As from from test first programming, those seem applicable outside of programming.

    • YAGNI -- painters don't do extra fancy trimming unless asked.
    • Pair programming -- people working in teams to check each other's work.
    • Collective code ownership -- rotating accounting personnel through various deparments so they can see the whole business.
    • Refactoring -
    • Re:Not really (IMHO), at least not for that reason (Score:1)

      by Adrian (66) <adrianh@quietstars.com> on 2004.01.05 17:40 (#27051) Homepage Journal

      I think you're reaching on some of those :-) For example you get a lot of synergy between the XP practices in programming that you don't get in other fields (it's hard to refactor a damp-proofing layer if you're a YAGNI painter!)

      I stiill think the XP practices are more about programming than project management.

      Reply to This

      Parent