Two is more than double of one

This week's reading talks about pair programming, a software development practice in which two developers work at the same time in the same project in the same thing in order to keep track of the work in case one misses. But it also improves times, productivity and software quality. The reading's goal is to facilitate the transition to pair programming by explaining how you already know how to do it.
The text begins explaining how pair programming in the XP methodology for development is really successful and how programmers attribute the success of their productivity and the methodology to the technique. And although many programmers tend to work alone and resit to the change, most of them  succeed in the transition to pair programming and begin loving it.
The first rule of pair programming is Share everything, even mistakes. The second one is play fair, meaning that you shall not take the control of the development and let the other person also be the one who codes. The third is Don't hit people which means not to waste other people time and make other people concentrate in the task they have instead of doing something else. The fourth Put things back where they belong which means to set thoughts aside and respect each other. The fifth Clean up your mess which means to correct the software mistakes you make or observe. Don't take things too seriously is to let the ego aside and accept that we all make mistakes. Say you're sorry when you hurt someone is to keep the communication with your partner good and in a violence free environment. Wash your hands before you start which means know your partner, talk. Flush: do everything in pairs, do not let any independent work enter the code without revision. Live a balanced life is to discuss but also work. Take a nap  is to separate from your partner for a break. When you go out into the world, watch out for traffic, hold hands and stick together means not to compete with your pair. And lastly, Be aware of wonder is to be prepared about working together enhancing your work.
I liked the reading because it makes the metaphor between kindergartner rules and pair programming tips, although I've never pair programmed I now have the initiative to try it.