1. Pair Programming

2. Who am I?
@_pedro_torres
Pedro Gustavo Torres

5. A little bit of background

6. What is Pair Programming?
• code is produced by two people programming:
– on one task
– on one workstation
• Two keyboards (optional)
• Two mice (optional)
• Two monitors mirroring (ideally)

7. Driver…

8. …navigator

9. Change roles multiple times a day

10. Change roles multiple times a day

11. Change roles multiple times a day

12. ¡Quiz time!
In which scenarios are the developers properly pairing?
A B
C D

14. Setup #1

15. Setup #2

16. Setup #3

17. Setup #4

18. Tackling multicultural barriers

20. All the times in front of…

21. …except in…

22. …and in!

24. Collective code ownership…

25. …bus factor…

26. …beginners mind

27. Pair rotation lader

28. What about code reviews?

30. The Rock Star…

31. …newbie…

32. …junior…

33. …senior…

34. …soul mates…

35. …CVDD…

36. …badass

38. Engagement / Commitment…

39. …valuable Stand ups…

40. …better integration of new team
members

42. Less bugs…

43. …more fun…

44. …less distractions…

45. …less interruptions…

46. …less slacking…

47. …and comfort zone wise…

48. …bigger comfort zone!

49. Two heads think better than one

51. “Common” habits…

52. …no music / social “stuff”

53. So is Pair Programming for everyone?

54. It should not be imposed

56. Remotely works?

57. Are estimations affected?

58. What about size or length of tasks?

59. Is it €xp£n$ive?

60. Is it only for mature teams?

61. Does it scale?

62. Companies that use it

63. Jobs?

64. Careers 2.0 by stackoverflow
428 Pair Programming jobs
422 JavaScript jobs
363 Java jobs
243 Python jobs
199 ASP .Net MVC
197 Ruby jobs
186 PHP jobs
175 Node.js jobs
132 Android jobs
120 iOS jobs
… on 16th of January 2014

65. Scholars and hands-on fans

66. Common pitfalls

68. Maybe slow…

69. …or Leeeeeeeeeeeeeroy!

70. Wrapping up

71. Thank you
Next time I’ll pair present! :P