2 / You must deal with different profile of programmers :
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
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
Comments
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