Full-Time Pair-Programming
•
0 likes•1,005 views
Full-time pair programming involves two developers working together on the same task or feature. It requires strong communication, coordination, and flexibility from both partners. Some benefits of pair programming include identifying problems quickly, asking others for help easily, staying focused on the task, and sharing knowledge across the team. It also helps developers learn new techniques from their partner. Maintaining good practices like switching partners and roles frequently helps avoid fatigue and keeps both developers actively involved.
Recommended
More Related Content
Viewers also liked
Recently uploaded
Recently uploaded (20)
Full-Time Pair-Programming
- 4. Solène Emilio Houssam Boris Olivier Mathieu Francis Romain PM PM RED TEAM Alexandre PM
- 7. DeadLift Powerlifting Personal Records DL Single Women 140 KG 120 KG 110 KG DL Single Men team of 3 persons
- 8. DeadLift Partner 120 KG DL Partner DL Partner Team DL Partner Balancing Weight/Height Pairing: two persons on the bar - team of 3 Pairing: one person changes every 5 reps
- 9. Harder with partner than solo especially at the start More Coordination More Communication size difference
- 10. Same Issues for Pair-Programming A must : Master the basics More qualities are needed
- 12. Accuracy Doing it right over and over again Fast is fine but Accuracy is everything (greek philosopher/warrior Xenophon) Lack of technique
- 13. Stamina Concentration even with Fatigue To Not Quit Pairing all the day is a tiring task
- 14. Flexibility Accept to experiment your pair’s ideas Accept to learn Accept to change make sure your pair is actively involved
- 15. Balance Work on all tasks Rolling Be polyvalent Swap Roles
- 16. Save Your Time pair-switching keyboard-switching Avoid dead-time context-switching
- 17. the more you Pair-Programming “programming out loud” the more you tolerate the sound, the noise around the more you talk Warning: the more you disturb solo workers around you
- 18. the more you pair-programming the less “You Are Asocial” oredev’15 - the myth of the asocial developer
- 20. Problems are identified quickly Average blocking time: 10-15 minutes Easily ask others for help
- 21. Focus on the task : No Mails, No Tweets
- 22. The code belongs to ALL THE TEAM
- 23. share knowledge see how others develop master your tools learn new techniques
- 24. Coach your pair and accept to be coached Conquer the weak points of the team always with concrete examples
- 25. by Xebia Essentials Cards
- 26. Anticipate problems No interactions No feedbacks
- 28. New comers Be patient Learn TeachShare hiring new look integration develop since the first day
- 30. keyboard No matter who have the but you should swap roles every few minutes
- 35. Routine is your enemy
- 36. My feedback Pair-Programming is a teamwork
- 37. TEAM Everyone has weak points Everyone has strong points Goals of the team Goals of everyone
- 39. zone de confort
- 40. Efficiency Measure you swap time
- 44. Mob-Programming
- 45. neXt I join yellow team next week
- 46. by Nike