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.
  • XP Prehistory (Score:4, Interesting)

    A number of XP's practices are quite old--Pair Programming dates back to punchard days, when the benefit of having an extra set of eyes look for problems could save a one day (or worse) compile/test cycle--but the genius of XP is in bundling the practices together. The self-supporting combination becomes much stronger than any one (or two or three) practices done in isolation.
    • Re:XP Prehistory (Score:4, Interesting)

      I think it's a bit of a stretch to date Pair Programming back to punched cards. There was a lot of 'desk checking', and asking others to look over card stacks and printouts. And, with the high cost of computing, there was a lot of debugging at the desk (both before and after a run), so many times, the second set of eyes was for debugging, not programming per se.

      But some of that is just picking nits. It doesn't matter a whole helluva lot if this is the earliest instance of pair programming, or a prototy

      • I think it's a bit of a stretch to date Pair Programming back to punched cards.

        Jerry Weinberg told me that John von Neumann's team at IBM used Pair Programming in much the same form that XP employs it now. That'd be back in the days of punchcards. And Jerry is savvy enough to understand the difference between Pair Programming and desk checking decks.