Post 1483793 by benoitj@linuxrocks.online
 (DIR) More posts by benoitj@linuxrocks.online
 (DIR) Post #1328270 by cbowdon@linuxrocks.online
       2018-11-19T18:43:19Z
       
       0 likes, 0 repeats
       
       Pair programming today with a colleague who is much better than me. Humbling and occasionally depressing, but a great workout.
       
 (DIR) Post #1328303 by djsumdog@hitchhiker.social
       2018-11-19T18:44:52Z
       
       0 likes, 0 repeats
       
       @cbowdon I always found pair programming incredibly stressful. I'm honestly not a big fan, but it's a great way to get people up to date on projects and concepts quickly. I don't it should be done for more than a day or two in a row though. I think code reviews are better for long term quality.
       
 (DIR) Post #1335226 by benoitj@linuxrocks.online
       2018-11-20T00:01:17Z
       
       0 likes, 0 repeats
       
       @djsumdog @cbowdon pair programming is one of the best way to learn. hard though if the pair does not match or needs practice at it. Even experienced coders are not good at it at first.Doing pair programming and mob programming almost every day with my 6 coders team and it takes a least 2 weeks of practice to becoming more fluid
       
 (DIR) Post #1407251 by cbowdon@linuxrocks.online
       2018-11-22T18:09:47Z
       
       0 likes, 0 repeats
       
       @benoitj @djsumdog I have found it difficult to work harmoniously when there is a skill imbalance. Having the junior drive while the senior advises works best to make sure both are active participants.It’s more stressful and tiring the bigger the skill gap (for me). But the skill gap decreases fast enough.
       
 (DIR) Post #1407721 by benoitj@linuxrocks.online
       2018-11-22T18:29:42Z
       
       0 likes, 0 repeats
       
       @cbowdon @djsumdog exactly, the one at the keyboard should do what the other is saying. I usually do something like: the driver (at the keyboard) listen to the navigator (not at the kbd). Nav start describing the intent, if needed the location, and if needed details. Change seat every 5 minutes and don't pair for more than 2 hours. Every x cycles, stop and discuss ways that work and areas to improve.
       
 (DIR) Post #1471968 by cbowdon@linuxrocks.online
       2018-11-25T09:50:58Z
       
       0 likes, 0 repeats
       
       @benoitj @djsumdog Sounds like good suggestions, especially nav giving high level guidance rather than specifics. Not sure about changing every 5 minutes though, that's a bit too disruptive for my tastes.
       
 (DIR) Post #1483793 by benoitj@linuxrocks.online
       2018-11-25T19:45:36Z
       
       0 likes, 0 repeats
       
       @cbowdon @djsumdog to my experience, the disruptive approach is what makes it work. Everyone is focus on the same goal and the solution is built collectively.