Slashdot Mirror
Experiences with Pair Programming?
gmletzkojr queries: "I recently was able to engage in some Pair Programming for a couple of days. However, my experience was less than rewarding. I have read books regarding the subject, and all of the case studies show praise for the effort. I found my pair programmer a bit difficult to work with. Has anyone been in this situation, and what things can be done to work around the personality conflicts?"
When I first looked at the comments this was my fortune:
It's hard to be humble when you're perfect.
Think that may relate to this issue, as others have commented on personality conflicts.
"Type foo"
"What?"
"There, foo"
"Oh yeah, ok"
"No, foo"
"Oh right"
"Oh for fuck sake.. FOO, the keyword is FOO"
"Oh sorry, was thinking about something else"
Pair programming is like watching a woman change channels. "You know what's on this channel, it's shit, keep going."
How we know is more important than what we know.
Hey! You were no rose either. And that whole printing routine was a farce. And its YOUR FAULT. I suggested something different but you had the keyboard. And speaking of which-you hogged the keyboard the whole freakin time too!
Driver: click, click, click, tappety-tap tap tap, click.
Observer: Dude, Intelli-sense just underlined that word in red. It's some kind of syntax error -- just hover your mouse over it to see it.
Driver: Ya, I saw it ... I just want to finish up what I'm typing and ...
Observer: It just underlined something else in your code. I don't think it's gonna' compile.
Driver: Of course it won't compile. Just wait until I finish this thought .... tap, tap, clickety click, tap-tap
Observer: I would fix those errors before continuing.
Driver: WHY? clackety-clack, slam, bang
Observer: Why not?
Driver: ARGH!
Observer: I'm bored. I'm just gonna' go grab another coffee.
Driver: GO AHEAD. AND WHILE YOU'RE AT IT, HAVE A SMOKE, AN EXTRA LONG LUNCH, AND THEN TAKE THE REST OF THE DAY OFF BECAUSE YOU'RE NOT LOOKING SO GOOD RIGHT ABOUT NOW.