To pair, or not to pair

To pair, or not to pair

A talk about pair programming, an agile development practice that still has only relatively patchy adoption across the industry. I talked about a few of the top benefits, then highlighted the challenges, and talked about why I believe those challenges are worth the hassle.

Presented at ThoughtWorks' XConf in New York in July 2018.

Video: https://www.youtube.com/watch?v=u_eZ-ae2FY8

645147e9899005bc24e5ff7d65a1d60c?s=128

Birgitta Boeckeler

July 20, 2018
Tweet

Transcript

  1. 3.

    “Betty Snyder and I, from the beginning, were a pair.

    And I believe that the best programs and designs are done by pairs, because you can criticise each other, and find each other’s errors, and use the best ideas.” Jean Bartik http://www.computerhistory.org/revolution/birth-of-the-computer/4/78/2258 1940s: The first programmers
  2. 6.
  3. 11.
  4. 12.
  5. 13.
  6. 14.
  7. 15.
  8. 16.
  9. 20.
  10. 21.
  11. 25.

    “To pair requires vulnerability. It means sharing all that you

    know and all that you don’t know. This is hard for us.” Tom Howlett, “The Shame of Pair Programming” https://diaryofascrummaster.wordpress.com/2013/09/30/the-shame-of-pair-programming/
  12. 27.

    IS IT WORTH THE HASSLE? CHALLENGES ENERGY INTENSE COLLAB. IT’S

    PERSONAL … EFFECTIVENESS 1+1>2 FOCUS CONT. INTEGRATION …
  13. 29.

    Pia Nilsson, “Knowing Me, Knowing You - Growing teams to

    continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes
  14. 30.

    Pia Nilsson, “Knowing Me, Knowing You - Growing teams to

    continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes Diversity
  15. 35.

    Pia Nilsson, “Knowing Me, Knowing You - Growing teams to

    continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes
  16. 36.
  17. 38.

    To Pair or not to Pair Do something today that

    your future self will thank you for. Birgitta Böckeler | @birgitta410