Not in code

This is from an amusing page on the c2 wiki.

The seven habits of effective pair-destroyers:

• Interrupt every time your partner starts doing something in a way other than how you’d do it.
• Insist on doing everything optimally the first time (even optimal keystrokes in the editor). Refactoring is not an option. Nothing fouls the current task better than PrematureOptimization and PrematureGeneralization.
• Don’t allow any idea you didn’t think of to be tried, no matter how small. Insist on being given a complete and conclusive argument that the idea will work and meets every standard of good code as practiced by the GreatOnes? before you yield even one keystroke. Refer to authoritative books to win such arguments.
• Cheat on ExtremeProgramming. Refuse to test first, do one task at a time, do what the customer asked, or any of the other practices that make pairing work. When reminded of the practices, argue and/or accuse.
• Once you wrestle the keyboard away, delete your partner’s last edit immediately. Then do what you were thinking of instead.
• Pair on stuff that is ambiguous so that you can diverge in intent and context every step of the way. (AmbiguityRequiresSpikes.)
• Never miss an opportunity to lecture your partner about good [OO-design|database-normalization|refactorings|math|linguistic-legalism]. Keep arguing and lecturing even after your partner agrees with you. Establish dominance.