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.
  • I mean you're a super CPAN magnet, with vast swathes of lovely code behind you. Stuff in Perl core, too. But for 90% of the rest of us that aren't so hot, it's a good idea. It tends to catch the really silly mistakes before the file even hits the disk. And the interface design ones too.

    -Dom

    • It's not really a matter of skill -- it's just the experience of sitting next to somebody and sharing a machine with them for hours at a time. It just crowds my space. I'm probably just being neurotic this way -- but I think a lot of programmers feel the same way.

      "I VANT TO BE ALOOOOONE."

      We are all Garbo now.

      • Yeah, a lot of programmers are scared to death of things they've never done before.

        • I'm not scared, I've done it and I hate it. I think in order for it to work one needs to be a much better multitasker than I am (eg I can't be on the phone and have someone nearby talking to me at the same time, as most humans can -- I'll lose track of both conversations). I can't be 100% concentrated on code and interact with someone at the same time. When I tried I made far more (stupid) mistakes than I usually do, and worse: when my pair pointed them out I failed to see them because I was focussed on

          --

          -- Robin Berjon [berjon.com]

          • That's fine; it doesn't work for some people. The University of Utah study showed only a 90% or higher uptake rate for pair programming. Of course, these were students and they did it consistently, for an assignment, for a couple of weeks.

            Take my comments with a grain of salt, though. The first programming class I ever took, back in the 80s, had too few computers and I had to pair. It didn't go well, partly because we were so very young and partly because we had no idea what we were doing.

        • I agree with TorgoX, and it is entirely, completely, absolutely unrelated to whether or not I have done it before.

          The two coders I work with the most are halfway across the country, and all the way across the country. I've not seen either one in close to two years. We work on IRC together, pointing out line numbers, pasting in code, emailing diffs. We keep the code in CVS and I we look over each other's changes. I much prefer that. Perhaps some things slip through the cracks that wouldn't in pair prog
      • Heh, another reason it's a good thing. It encourages you to get up and go away from the computer more often. :-)

        -Dom