Pairing

We know that programming is not merely typing — we're constantly solving problems and making many small decisions throughout the process. Working on a problem together is a great way to learn from each other, leverage multiple views on a problem, and enable review to happen earlier and concurrently with building.

Benefits of pairing:

• mentoring + coaching - we can't expect junior team members to learn how to work if they never get to see anyone work
• multiple perspectives on a problem can spot issues earlier (issues found late require more effort to discover, document, reproduce and fix)
• learn by seeing how others work to tackle problems, communicate, use tools, etc.
• increased shared knowledge of codebase and coding practices
• less need for review as coding is not happening in silos

It should be noted that learning to pair effectively can take time. You might not be great at it right away, but over time it can become an effective tool in your toolbox. If you're a senior+ developer, it's part of your responsibility to teach juniors and help them level up and pairing is one way to do that.