Re:There is no “us” in team
by username90 on Friday June 18, 2021 @12:26PM
(#27552019)
The review you do when pairing isn't a proper review though. The point is to have someone who wasn't there during implementation look at it, while with pairing both people will have similar biases about the code.
But as you put it, any non-trivial task, e.g. where you're creating multiple new classes and refactoring along the way is hard to do with pair programming.