A short introduction to Pair Programming

How to write better code without killing each other

Transcript

1. PAIR PROGRAMMING OR HOW TO WRITE BETTER CODE TOGETHER WITHOUT KILLING EACH OTHER
2. WAT? 2 PROGRAMMERS ON 1 WORKSTATION
3. DRIVER ! CODING NAVIGATOR ! READ CHECK SANITY TEST DIRECTION WAT?
4. SWAP ROLES WAT?
5. CODE QUALITY ! BETTER THOUGHT CODE LESS SLOPPY LESS TRIVIAL ERRORS BENEFITS
6. BENEFITS MORE KNOWLEDGE ! ON THE PROJECT NEW TRICKS SKILLS TRANSFERT
7. BENEFITS PROJECT ! REDUNDANCY RESILIENCE
8. BEST CASE SCENARIO ! OVERHEAD INCREASE 15% COSTS
9. PAIR PROGRAMMING + TDD ! 10 DEV_1 WRITES A FAILING TEST 20 DEV_2 WRITES THE CODE TO MAKE THE TEST PASS 30 DEV_2 WRITES THE NEXT FAILING TEST 40 SWAP(DEV_1, DEV_2) 50 GOTO 10 PING PONG VARIANT
10. AND NOW?
11. FIDOR TECS PROJECT DATE CLIENT TBD OUR PLAN 2 HOURS / DAY ; 1 PAIR / WEEK ; 1 TASK / PAIR