If there is a single go-to guy for certain problems, that is a risk, a single point of failure. The way we learn to code in school is actually promoting these risks. In school we're encouraged to solve problems alone and we take our time to do that. In production environments it is important to have more than one go-to guy for every problem. It is worth considerable investment to get there. When Pair Programming is done right the reduction in peak productivity compared to all team members programming alone is offset by its unique benefits: there are no single points of knowledge and the overall quality is higher because all code is peer reviewed. Programmer pairs tend to be more resilient to distraction than programmers alone.

Topics in this 2-day workshop are:

• effective pairing
• remote pairing