Pair programming is a technique that might help you to reduce the bottleneck that a Pull Request represents for your team at the time of reviewing the code.
Personally I have never pair programmed. I assume you are rotating your pairs regularly so that knowledge silos are not created. In my case, I'm on-call for any changes that anyone in my team does, so being involved in regular code reviews help my own understanding of the codebase
Yes, we rotate, between the pair (driver & and compass), and mixing pairs too (changing pairs), so the silos "should" not happen. For me this is the most difficult part: Change the pair and get up to speed as soon as possible to start typing
Interesting your learnings, Marcos.
Personally I have never pair programmed. I assume you are rotating your pairs regularly so that knowledge silos are not created. In my case, I'm on-call for any changes that anyone in my team does, so being involved in regular code reviews help my own understanding of the codebase
Yes, we rotate, between the pair (driver & and compass), and mixing pairs too (changing pairs), so the silos "should" not happen. For me this is the most difficult part: Change the pair and get up to speed as soon as possible to start typing