In February 2016, I celebrated my 4th anniversary developing using full-time pair-programming. By full-time I mean that when I arrive in the morning at work I do not have my own computer. I share a computer all the day with another developer of my team. At first sight, it might look easy, amazing and a kind of luxury. Instead of having one person to develop a new functionality we have two persons that work together on it. In reality, it is a tiring but exciting work: ‘Tiring’ because you need to have more skills than solo developers. ‘Exciting’ because it challenges you and if it does not challenge you it does not change you. In this talk, I’ll focus on the challenges and the main benefits of this kind of pair-programming for you, for your team and for your company: How you can make the most of this kind of programming? How each pair can boost his partner? How you can improve your technique of pairing? How you can anticipate problems and fix them? What are the common errors about pairing?

1. Never Develop
Alone
Always With a
partner2016 Edition

2. #AskMe
@houssamfakih

3. All content appearing in this presentation
are not from fictitious or novel. All
characters are real Not from any
imaginary world. Any resemblance with
the sport's world should not be
considered as purely coincidental
Disclaimer:
@houssamfakih

4. FULL-TIME
Pairing
@houssamfakih

5. PART-TIME
Pairing
@houssamfakih

6. 100% Pairing
since 4 years
@houssamfakih

7. @socrates_fr

9. Portfolio Analytics & Services to the
Global Asset Management Industry

10. New Version
for
#itakeunconf
@houssamfakih

11. Why you
should
always pair?
@houssamfakih

12. @houssamfakih

13. In a
Perfect
World
@houssamfakih

14. @houssamfakih
More
Focus

15. No Mails
No Tweets
@houssamfakih

16. More Confident
@houssamfakih

17. Feedback @houssamfakih

18. Share Knowledge
@houssamfakih

19. More Fun
@houssamfakih

20. Never Blocked
More than 10’
@houssamfakih

21. More
Free@houssamfakih

22. Easy
Onboarding
@houssamfakih

23. Continuous
Improvement
@houssamfakih

24. Less Blames @houssamfakih

25. In Real
world @houssamfakih

26. @houssamfakih

27. @houssamfakih

28. @houssamfakih

29. In Pairing, the keyboard Is Everything
@houssamfakih

31. @houssamfakih

32. Driver Watcher
Is Insane
@LebettreC
@houssamfakih

33. @houssamfakih

34. Keyboard should
Swaps naturally
@houssamfakih

35. Keyboard
Moves
@houssamfakih

36. Ways to prevent
Keyboard
Monopolisation
@houssamfakih

37. @coreyhaines
I do recommend the form 2

38. Timeboxing
Max 5’
@houssamfakih

39. Two Keyboards @houssamfakih

40. Coordination @houssamfakih

41. Avoid
Driver/Twitterer
@coreyhaines

42. Ask You Pair
To Pay
Attention @houssamfakih

43. Make a plan
with your pair
@houssamfakih

44. Share Your
Thoughts @houssamfakih

45. Think
Loudly
@houssamfakih

46. Make sure
everyone is
actively involved
@houssamfakih

47. Ask You Pair
To Slow Down
@houssamfakih

48. @houssamfakih

49. Measure
Switching
Time @houssamfakih

50. Flexibility
@houssamfakih

51. Never Force a solution
@houssamfakih

52. Accept to
experiment
new ideas @houssamfakih

53. Accept
Feedback
@houssamfakih

54. Be
Nice
@houssamfakih

55. @houssamfakih

56. Support
Your
Team
@houssamfakih

57. Celebrate
Success
@houssamfakih

58. Mob-Prog
as often as
you can @houssamfakih

59. Consistency@houssamfakih

60. Balance
@houssamfakih

61. Does It Work
for everyone?
@houssamfakih

62. Solo vs Teamwork @houssamfakih

63. Solo vs Teamwork @houssamfakih

64. @houssamfakih

65. @houssamfakih

66. Questions ?

67. Credits
● Coach Nathalie for my first workout with deadlift partner https://www.facebook.com/natalie.
lahoussinerios
● Corey Haines, Four Rules of Simple Design https://leanpub.com/4rulesofsimpledesign
● Photos: pixabay