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
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
What XP Ought To Be Called (Score:1)
Re:What XP Ought To Be Called (Score:2, Informative)
They got the Linux kernel wrong, then, as "refactoring" should be called "throwing it all away and starting over from scratch every release" and "automated testing" should be "ask users to debug it for you and berate them for not reading the development mailing list religiously". :)
Lots of open source projects succeed because their leaders are exceedingly brilliant at project management without discipline. Lots more projects succeed because there's a point at which you can throw many, many warm bodies at
Re:What XP Ought To Be Called (Score:1)
1) workers aren't forced to work on the boss's bad ideas -- the bad ideas
have to attract the workers on their own (see apache.org java stuff
2) no boss deadline pressure
3) no boss backward-compatibility pressure
These three things are, in my experience, responsible for the bulk of stupidity
in boss-run proprietary software organizations.
Now, of course,
Re:What XP Ought To Be Called (Score:3, Interesting)
But how can you say the Perl 5 guts don't have backward-compatibility pressure? :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:What XP Ought To Be Called (Score:3, Funny)
Let's not talk about backward pressure in guts, please. There might be children present.
Reply to This
Parent