Pair programming explanation and some advises about how to success doing it.

1. Pair programming

2. Benefits
● Less bugs.
● Better code quality.
● Spreads business knowledge in the team.
● Creates a learning environment.
● Improves communication.

3. We should pair when...
● Complex features.
● Critical features.
● Core libraries.
● New part of the system.
● The team has a new member.

4. We should not pair when...
● One person is sick.
● Spiking code.
● Trivial tasks that don’t add value.
● The other person do not agree to pair.

5. Some techniques
● Driver - Navigator
● Ping - Pong

6. Driver - Navigator
● Driver:
○ Is the person typing the code.
● Navigator:
○ Helps driver.
○ Reviews what the driver is writing.
○ Keeps in mind the whole picture.
● Benefits:
○ Makes sure everybody is contributing.

7. Ping - Pong
● Driver:
○ Writes code.
● Navigator:
○ Writes the tests.
● Benefits:
○ Another developer evaluates functionality.
○ Learn about Test Driven Development (write the tests before the production code).

8. Some tips...
● Keep personal space.
● Clean desktop environment.
● The developers should be at the same distance from the monitor/s.
● Know the goals.
● Set timing, 4-6 hours per day.
● Change the roles frequently, at least once an hour.
● Rotate team members.

9. More tips…
● Pair programming is a negotiation.
● If you are bored pass the keyboard.
● If your partner is bored grab the keyboard.
● If both are bored, take a break.
● Talk a lot, this is about communication.
● If you do not understand what your partner is saying or doing, just ask.

10. Extra tip...
10-seconds rule
The navigator should wait 10 seconds before pointing out a typo. Generally
that is long enough for the driver to correct a typo that is already noticed.
Excessive interruptions are distracting.