how-to-pair-programming.md

Pair programming resources

Reading materials

• UK gov article: https://gds.blog.gov.uk/2018/02/06/how-to-pair-program-effectively-in-6-steps/
  My takeaway: give enough mental, physical time (can be more than 2 hours) for pair programming. Set up a goal of pair programming before starting.

• from thoughtworks: thoughtworks.com/insights/blog/10-ways-improve-your-pairing-experience
  My takeaway: Manage fatigue and focus (suggesting Pomodoro, having break during pair) well during pair programming.Restrain yourself from putting the priority on moving fast.

• how to adopt... etc: https://medium.com/@jdxcode/how-to-pair-program-d6741077e513

• pairing with junior: https://madeintandem.com/blog/2015-1-pairing-with-junior-developers/
  My takeaway: It is better for seniors not to type to prevent seniors from solving all problems by themselves. Try asking questions that can lead junior better rather than micro managing junior. Also, seniors should be open about not knowing, and learning from juniors.

• code review vs pair programming : https://medium.com/@vanessasantanna/pair-programming-and-pull-requests-different-ways-to-get-code-review-done-861bca922209
  My takeaway: pair programmed code means it doesn't need an additional code review. Pair programming can transfer tacit knowledge while code review can strengthen codified knowledge.

• pair programming from junior perspsecitve: https://speakerdeck.com/itsyganok/pair-programming-from-a-beginners-perspective?slide=14

• Tuple's guide for pair programming (This is quite step by step, probably will be a good read for everybody): https://tuple.app/pair-programming-guide

• ultimate! : https://martinfowler.com/articles/on-pair-programming.html

Tactics

1. Driver & Navigator :Driver types, Navigator suggests the idea. Navigator should not micro manage Driver (ex. saying ‘type console.log(…)). Change the role every ~20 mins or every small task finished.
2. Ping pong: A develops a (failing) test, while B implements the feature to make the test pass.
3. Mob: showing code to more than one person, make progress as getting more feedbacks. Change the presenter every 10,15 mins
4. Strong: Similar to Driver & Navigator, but when Navigator has much more experience. This pair is mainly to transfer the knowledge. Driver just follows Navigator’s suggestions, and they don’t change the role.
5. Pair development: There are many things other than programming that can be solved through pair. You can agree on what to achieve, architect the code... etc. In a case that might not be efficient to pair ex. Developers working with tools that neither is familiar with, so need some discovery works. you can make a list of questions that need to be answered and distribute tasks, and meet later.

Tools

• Tuple: https://tuple.app/?ref=producthunt
• VSCode live share: https://code.visualstudio.com/blogs/2017/11/15/live-share

My questions

• any tool worked for remote pairint?
• our devs expertise will often make problems from senior vs junior pair. How can we make this work?
• How often? what kind of task wored the best with pair?