great video.
But you only scratch what I consider blockers for Pair Prog.
1 / You need your team to have pple skills :
We are talking of 2h to full days of pair with someone on your back, it can be intimidating or exhausting.
But you only scratch what I consider blockers for Pair Prog.
1 / You need your team to have pple skills :
We are talking of 2h to full days of pair with someone on your back, it can be intimidating or exhausting.
Comments
It’s possible that somehow, magically, the teams I worked on had these skills by accident, but I don’t think so. I think pairing helps teams to get better at working together, that’s part of the win.
Taking the definition of @woodyzuill.bsky.social's book, to get the idea from your brain into the computer, it has to go via someone else's hands.
Good pairing forces you to explain the IDEA to your peer, who then turns it into code.
In my experience, doing driver-navigator well is also what avoids the issue SylRob mentioned.
@davefarley77.bsky.social did you ever create a video on driver/navigator? You may have, but off the top of my head I don't recall any 🤔
https://youtu.be/aItVJprLYkg
Driver/navigator is briefly mentioned at the beginning and then again from the 20 minute mark onwards.
I also can't recommend @woodyzuill.bsky.social's amazing book enough.
https://a.co/d/cqOhqMu
https://www.manning.com/books/unit-testing
mixing dev that want to start coding first and fix the errors with dev that wants to spend the first hours reading the docs. This can create frustration and conflicts
I don't like the word "trust" here but it mean that you have a team with at least enough senior dev to pair with junior.
If the idea is to review each other or create reliable tests with each feature, can you really trust 2 junior pairing ?...
in order to put pair programing practice in your team, I am guessing you need to organize the pair daily, try to mix evenly the pple of your team depending on their expertise and seniority, etc... and for me this also looks quite heavy TBH