Pair Programming
Pair programming is a good practice to avoid an uncommunicative state. Expecially that moment that some developer callas "The flow zone". There are moment were a developer think to be infallible. Those moment he write more code. TDD become faster and easy to do. This is the right feeling to do pair programming and practicing katas. The reason is that during pair programming pairs must communicate!
Ping Pong
During pair programming it is possible to play ping pong. As described in first pages of this book developers should
- a player'll receive code with a red test
- same player'll write production code to keep test suite in green;
- eventually refactor the code;
- leave keyboard to another player
This methodology is my favorite because of interactions. Here we have interactions.