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.
  • More myths (Score:2, Interesting)

    Hmm... I've come across too many to mention. Particularly common ones include:

    • "Pair programming doesn't work" said by people who have never tried it (I also believe there are people who actually cannot get along pair programming - but that's a different group from those who have never tried it :-)
    • "YAGNI/Do the simplest thing will result in bloated inefficient code" - because they completely ignore the whole refactoring bit.
    • "You cannot schedule a project properly" - because they didn't actually read that whole bit on release planning. This is one of those things I really want to jump up and down about. My XP(ish) experiences have given me much better results on the scheduling front.
    • "We cannot integrate more than once a week, it takes too long" - not realising that if they integrated a couple of times a day they wouldn't get the problems that mean they only do it once a week.
    • "We need to work 60 hour weeks to meet the deadline" - no you don't. Really. You don't. You end up working slower.

    It seems odd to me that people can go and read the white book and just forget half of what was written there. Most odd.

    • I like the "XP doesn't work because I don't think I'd like pair programming". Someone on the XP mailing list gave a nice analogy:

      This cake recipe makes awful cake! I ate the cup of flour it calls for and didn't care for it at all.