Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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

    • 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 -