Paring technical sessions for kick-offs and reviews can be a good alternative for programmers frustrated with async code reviews and unhappy with continuous pair programming.
Pairing vs. Code Review: Comparing Developer Cultures Prerequisites for success There are a few nonnegotiables that are common across both of these paradigms. Solid continuous integration Talented core developers Agreement on the importance of code quality Iterative self-organization The joys of pairing Everybody gets better together Pairing can balance the natural daily ebbs and flows of energy A peer generates motivation for self-improvement Tactical decisions are made more easily and with better results [Stronger] concept of collective code ownership but,...