I'm genuinely wondering: is pair programming better, compared to doing the design in pair, going to work on your own, then reviewing each other's code?
As an introvert I don't think I could handle the "pair all day" approach.
> is pair programming better, compared to doing the design in pair, going to work on your own, then reviewing each other's code?
The literature is, I believe, pretty thin and equivocal. However the suspicion is that pair programming is pretty much the core loop of bouncing back and forth, reduced to the smallest possible size.
It also avoids some of the antipatterns I've seen with code reviews -- widely distributed patches, reviews getting stale because they were too hard for a Monday, then a Tuesday... then a Friday ...
> As an introvert I don't think I could handle the "pair all day" approach.
You can take a break if you need one. Lunchtime is fixed at an hour. I typically go and spend it alone with a book.
There is sometimes a confusion between intro/extraversion and sociability. I'm quite sociable, I genuinely like talking to people, but it drains me because I lean towards introverted. So the lunchtime recharge is very helpful.
The literature is, I believe, pretty thin and equivocal. However the suspicion is that pair programming is pretty much the core loop of bouncing back and forth, reduced to the smallest possible size.
It also avoids some of the antipatterns I've seen with code reviews -- widely distributed patches, reviews getting stale because they were too hard for a Monday, then a Tuesday... then a Friday ...
> As an introvert I don't think I could handle the "pair all day" approach.
You can take a break if you need one. Lunchtime is fixed at an hour. I typically go and spend it alone with a book.
There is sometimes a confusion between intro/extraversion and sociability. I'm quite sociable, I genuinely like talking to people, but it drains me because I lean towards introverted. So the lunchtime recharge is very helpful.
Each pair finds their own balance.