PAIR PROGRAMMING
OR HOW TO WRITE BETTER CODE TOGETHER WITHOUT
KILLING EACH OTHER
Slide 2
Slide 2 text
WAT?
2 PROGRAMMERS ON 1 WORKSTATION
Slide 3
Slide 3 text
DRIVER
!
CODING
NAVIGATOR
!
READ
CHECK
SANITY TEST
DIRECTION
WAT?
Slide 4
Slide 4 text
SWAP ROLES
WAT?
Slide 5
Slide 5 text
CODE QUALITY
!
BETTER THOUGHT CODE
LESS SLOPPY
LESS TRIVIAL ERRORS
BENEFITS
Slide 6
Slide 6 text
BENEFITS
MORE KNOWLEDGE
!
ON THE PROJECT
NEW TRICKS
SKILLS TRANSFERT
Slide 7
Slide 7 text
BENEFITS
PROJECT
!
REDUNDANCY
RESILIENCE
Slide 8
Slide 8 text
BEST CASE SCENARIO
!
OVERHEAD INCREASE
15%
COSTS
Slide 9
Slide 9 text
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
Slide 10
Slide 10 text
AND NOW?
Slide 11
Slide 11 text
FIDOR TECS
PROJECT
DATE CLIENT
TBD
OUR PLAN
2 HOURS / DAY ; 1 PAIR / WEEK ; 1 TASK / PAIR