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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
XP is Overcomplicated (Score:1)
Flashback to "XP and Open Source"... (Score:1)
Okay, so I might be a little bitter because I'm writing unit tests for Everything [sf.net], exposing and fixing several bugs and trying to figure out how some features ever worked. :)
Reply to This
Parent
Re:Flashback to "XP and Open Source"... (Score:1)
Our biggest problem is documentation, which as I understand (?) XP isn't big on to begin with.
Re:Flashback to "XP and Open Source"... (Score:1)
Dare I suggest "Issue Mode" as a Slash feature which seems to work, yet defies all resonable attempts at explanation?
I can't point at any one particular source, but don't believe XP eschews API or end-user documentation. The idea seems to be "Travel Light" (no adverb, sadly). PERT charts, UML diagrams, reams of detailed specifications, and even code comments have a way of going out of date. XP suggests to avoid them, unless they really help.
(Of course, if I were strict I'd say "NO documentation wo
Re:Flashback to "XP and Open Source"... (Score:1)
As to some of the metamoderator code, I do not accept your dare to look at it.
Re:Flashback to "XP and Open Source"... (Score:2)
The best source to point to is Beck's Extreme Progamming Explained. The party line is that the individual aspects of XP are self-reinforcing, but only when practiced under ideal