- Set up a video call with your partner - Slack is probably easiest, but you can also use Zoom or Google Meet if you and your partner prefer.
- Make a copy of the Pair Programming Contract and fill it out with your partner (click File > Make a Copy).
- When you're ready to start on the lab, one person should fork the lab. Remember: only one person should fork the lab.
- That person should then add their partner as a collaborator to the repo.
- Both partners should clone down the repo by running
git clone.
- Driver: the person who types the code
- Navigator: the person who guides the driver and decides how to approach the problem
- Check in with your partner
- Agree on the ground rules
- Make a plan
- Get comfortable
- CODE!
- Decide who will start as driver and who will navigate, and agree on when you will switch (30 minutes is a good rule of thumb)
- When you’re ready to switch roles, the driver should run these commands (make sure you are in the root directory of the project first by typing
pwdin your terminal!):
git add .
git commit -m 'some commit message'
git push
- The new driver should then run
git pullto download the new code.
It’s not required that both partners submit the lab on Learn. Only the person who forked the lab will able to submit. (If you really want to submit, whoever didn’t fork the lab initially will have to also fork and copy the code that you worked on together).
More importantly, make sure to give feedback to your partner! Talk to your partner about how you want to receive feedback (written or spoken), and fill out this Feedback Form to help collect your thoughts and to give staff insight into your pairing experience.
Feedback should be Consensual, Actionable, Specific, and Kind. Giving and receiving feedback can be hard, but it’s an important skill to develop and will also help you and your peers improve the next time you are given a pairing assignment.