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 remember pairing with you fixing a segfault and being in the zone. It's a different kind of zone altogether, I think.

    Is it reasonable for a company to really want to potentially inhibit the productivity of Bobs by making them pair?

    That depends. How did you measure Bob's productivity with and without pairing? How did you measure the quality and efficacy of his code?

    • I think, if anything, it's a different type of zone. We didn't pair much, but I think when we did, we got stuff done and it was good. There are others that I pair with and it seems almost impossible to get work done. However, it's tough for me to prove this. I can only claim these are my observations and without the resources to do a proper study, I can only make generalizations that I am hard-pressed to back up.

  • What you're describing sounds like an attempt to pair without the team having agreed to adopt some of the XP practices that support pairing--refactoring being one. If people can say "ooh, that'd be too abstract" and get away with it, or can dismiss refactoring as being out of scope, then, good developers or not, you have a larger problem than just pairing. Pairing is just exposing the problem(s).

    As an aside, you missed one benefit of pairing: Pairing keeps developers from getting blocked. In particular,

    • I think you've hit some key points. I would agree that the team has not bought all of the XP tenets, though to a certain extent, I think it's incumbent upon management to help them along there. Still, if the team isn't entirely sold on the benefits, I think this makes the situation more difficult and means that we either need to find a way to better strengthen our XP practices, or find ways of gaining the benefits that the programmers agree to.

      And yes, I did forget about pairing helping to overcomes blo

  • Funny, but my experience is pretty much the opposite. Pairing helps me stay in the zone (okay, Pairing and TDD in combination). Pairing because I get burned out less, if I get tired my pair will start driving. TDD because it makes getting back into the zone very easy because I know exactly what I was doing - making the next test pass.

    These are really interesting posts BTW. Have you considered posting them to the extremeprogramming@yahoogroups.com list too? I'm sure people would find it interesting, and yo

    • I started to write a long reply but I realized that some of what I wanted to say would be inappropriate for a public journal. Suffice it to say that there are other issues and not being able to discuss all of them openly distorts what's going on. I tried to be fair in the parent post, but there's only so much I can do.

      And I'm glad you find the posts interesting. I hadn't thought about posting this the yahoogroups list. I'm afraid of being burned at the stake :)

      • And I'm glad you find the posts interesting.

        I, for one, was a little bit shocked when I looked at the parent post and saw how long it was, but it turned out to be a very good reading :-) Thanks :-)

      • I tried to be fair in the parent post, but there's only so much I can do.

        I hope it was obvious that I wasn't trying to criticise, just offer an alternate experience. If not, apologies :-)

        I hadn't thought about posting this the yahoogroups list. I'm afraid of being burned at the stake.

        They've not bitten my head of yet!