ihollander · February 5, 2021 23:33 · Aug 5, 2020 · Aug 5, 2020 · Aug 5, 2020 · Aug 5, 2020
diff --git a/pairing.md b/pairing.md
@@ -38,4 +38,8 @@ Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.c
 
 ## Links
 - [Pairing Slides](https://docs.google.com/presentation/d/1gB7DDJcOm7FE11A1pa214RHPd76c2h2plyWeQWO07uQ/edit?usp=sharing)
-- [Pairing Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit)
+- [Pairing Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit)
+- [Screen Sharing with Slack](https://slack.com/help/articles/115003501303-Share-your-screen-with-Slack-calls#from-a-dm-1)
+- [Adding Collaborators with Github](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)
+- [Feedback Form](https://forms.gle/Nx8UyMxEGFRm6t6M6)
+- [How to give feedback](https://medium.com/unsupervised-learning/giving-actionable-specific-and-kind-feedback-6fc83eb04a65)
diff --git a/pairing.md b/pairing.md
@@ -38,5 +38,4 @@ Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.c
 
 ## Links
 - [Pairing Slides](https://docs.google.com/presentation/d/1gB7DDJcOm7FE11A1pa214RHPd76c2h2plyWeQWO07uQ/edit?usp=sharing)
-- [Pairing Notes](https://docs.google.com/document/d/1x5UJk5FJ2MGNtkAR48-RdpQiUzoHARNbdfluWR8miIk/edit)
 - [Pairing Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit)
diff --git a/pairing.md b/pairing.md
@@ -2,6 +2,7 @@
 
 ## Setup
 
+1. Set up a video call with your partner - [Slack](https://slack.com/help/articles/115003501303-Share-your-screen-with-Slack-calls#from-a-dm-1) is probably easiest, but you can also use Zoom or Google Meet if you and your partner prefer.
 1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner (click File > Make a Copy).
 1. When you're ready to start on the lab, **one person** should fork the lab. Remember: only **one person** should fork the lab.
 1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.

diff --git a/pairing.md b/pairing.md
@@ -31,7 +31,9 @@ git push
 ## When you’re done
 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! Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.com/unsupervised-learning/giving-actionable-specific-and-kind-feedback-6fc83eb04a65). 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.
+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](https://forms.gle/Nx8UyMxEGFRm6t6M6) to help collect your thoughts and to give staff insight into your pairing experience.
+
+Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.com/unsupervised-learning/giving-actionable-specific-and-kind-feedback-6fc83eb04a65). 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.
 
 ## Links
 - [Pairing Slides](https://docs.google.com/presentation/d/1gB7DDJcOm7FE11A1pa214RHPd76c2h2plyWeQWO07uQ/edit?usp=sharing)

diff --git a/pairing.md b/pairing.md
@@ -11,9 +11,16 @@
 - **Driver**: the person who types the code
 - **Navigator**: the person who guides the driver and decides how to approach the problem
 
+## Before You Start
+- Check in with your partner
+- Agree on the ground rules
+- Make a plan
+- Get comfortable
+- CODE! 
+
 ## Switching Roles
 1. 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)
-2. 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 pwd in your terminal!): 
+2. 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 `pwd` in your terminal!): 
 ```
 git add .
 git commit -m 'some commit message'

diff --git a/pairing.md b/pairing.md
@@ -3,7 +3,7 @@
 ## Setup
 
 1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner (click File > Make a Copy).
-1. **One person** should fork the lab. Only **one person** should fork the lab.
+1. When you're ready to start on the lab, **one person** should fork the lab. Remember: only **one person** should fork the lab.
 1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.
 1. Both partners should clone down the repo by running `git clone`.
 

diff --git a/pairing.md b/pairing.md
@@ -24,4 +24,9 @@ git push
 ## When you’re done
 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! Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.com/unsupervised-learning/giving-actionable-specific-and-kind-feedback-6fc83eb04a65). 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.
+More importantly, make sure to give feedback to your partner! Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.com/unsupervised-learning/giving-actionable-specific-and-kind-feedback-6fc83eb04a65). 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.
+
+## Links
+- [Pairing Slides](https://docs.google.com/presentation/d/1gB7DDJcOm7FE11A1pa214RHPd76c2h2plyWeQWO07uQ/edit?usp=sharing)
+- [Pairing Notes](https://docs.google.com/document/d/1x5UJk5FJ2MGNtkAR48-RdpQiUzoHARNbdfluWR8miIk/edit)
+- [Pairing Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit)
diff --git a/pairing.md b/pairing.md
@@ -5,7 +5,7 @@
 1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner (click File > Make a Copy).
 1. **One person** should fork the lab. Only **one person** should fork the lab.
 1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.
-1. Both partners should clone down the repo with git clone
+1. Both partners should clone down the repo by running `git clone`.
 
 ## Roles
 - **Driver**: the person who types the code

diff --git a/pairing.md b/pairing.md
@@ -3,7 +3,7 @@
 ## Setup
 
 1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner (click File > Make a Copy).
-1. One person should fork the lab.
+1. **One person** should fork the lab. Only **one person** should fork the lab.
 1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.
 1. Both partners should clone down the repo with git clone
 

diff --git a/pairing.md b/pairing.md
@@ -2,7 +2,7 @@
 
 ## Setup
 
-1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner.
+1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner (click File > Make a Copy).
 1. One person should fork the lab.
 1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.
 1. Both partners should clone down the repo with git clone

diff --git a/pairing.md b/pairing.md
@@ -19,7 +19,7 @@ git add .
 git commit -m 'some commit message'
 git push
 ```
-3. The new driver should then git pull to download the new code.
+3. The new driver should then run `git pull` to download the new code.
 
 ## When you’re done
 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).

diff --git a/pairing.md b/pairing.md
@@ -7,10 +7,11 @@
 1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.
 1. Both partners should clone down the repo with git clone
 
-## Switching roles
-**Driver**: the person who types the code
-**Navigator**: the person who guides the driver and decides how to approach the problem
+## Roles
+- **Driver**: the person who types the code
+- **Navigator**: the person who guides the driver and decides how to approach the problem
 
+## Switching Roles
 1. 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)
 2. 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 pwd in your terminal!): 
 ```

diff --git a/pairing.md b/pairing.md
@@ -1,32 +1,26 @@
-# How to pair with Github
-We'll be working on this practice lab: https://github.com/Guillamoure/prework-library-loops
+# How to Pair
 
 ## Setup
 
-### Partner 1:
-- Fork this repo: https://github.com/Guillamoure/prework-library-loops
-- This should take you to a new page on Github for your forked repo: https://github.com/YOUR_NAME/prework-library-loops
-- Click the Settings tab, then Manage access in the sidebar
-- Click Add Collaborator and enter your partner's github username
-- Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-- Then type `cd prework-library-labs` to go into the project directory and type `code .` to open in VSCode
+1. Make a copy of the [Pair Programming Contract](https://docs.google.com/document/d/1ce3zFnY_z3VoVQNmpqQHt1Bm00l8HThioPubD80Haq4/edit) and fill it out with your partner.
+1. One person should fork the lab.
+1. That person should then [add their partner as a collaborator](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) to the repo.
+1. Both partners should clone down the repo with git clone
 
-### Partner 2:
-- After your partner adds you as a collaborator, you'll receive an email to collaborate on the repo
-- Once you've accepted the invite, go to your partner's fork of the repo: https://github.com/YOUR_PARTNERS_NAME/prework-library-loops
-- Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-- Then type `cd prework-library-labs` to go into the project directory and type `code .` to open in VSCode
+## Switching roles
+**Driver**: the person who types the code
+**Navigator**: the person who guides the driver and decides how to approach the problem
 
-## Workflow
-- Decide on driver/navigator roles
-- The driver should share their screen and work on the code from the repo they cloned
-- When it's time to switch roles, the driver should commit their code:
-
-```sh
-$ git add .
-$ git commit -m 'some descriptive commit message'
-$ git push
+1. 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)
+2. 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 pwd in your terminal!): 
+```
+git add .
+git commit -m 'some commit message'
+git push
 ```
+3. The new driver should then git pull to download the new code.
+
+## When you’re done
+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).
 
-- Then, the new driver should pull down the new version of the code: `git pull`
-- For now, we're just using one branch for simplicity - in the future, you'll use different branching strategies depending on your workflow
+More importantly, make sure to give feedback to your partner! Feedback should be [Consensual, Actionable, Specific, and Kind](https://medium.com/unsupervised-learning/giving-actionable-specific-and-kind-feedback-6fc83eb04a65). 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.
diff --git a/paring.md → pairing.md b/paring.md → pairing.md
diff --git a/paring.md b/paring.md
@@ -9,13 +9,13 @@ We'll be working on this practice lab: https://github.com/Guillamoure/prework-li
 - Click the Settings tab, then Manage access in the sidebar
 - Click Add Collaborator and enter your partner's github username
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-- Then `cd` into the project directory and type `code .` to open in VSCode
+- Then type `cd prework-library-labs` to go into the project directory and type `code .` to open in VSCode
 
 ### Partner 2:
 - After your partner adds you as a collaborator, you'll receive an email to collaborate on the repo
 - Once you've accepted the invite, go to your partner's fork of the repo: https://github.com/YOUR_PARTNERS_NAME/prework-library-loops
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-- Then `cd` into the project directory and enter `code .` to open in VSCode
+- Then type `cd prework-library-labs` to go into the project directory and type `code .` to open in VSCode
 
 ## Workflow
 - Decide on driver/navigator roles

diff --git a/paring.md b/paring.md
@@ -9,13 +9,13 @@ We'll be working on this practice lab: https://github.com/Guillamoure/prework-li
 - Click the Settings tab, then Manage access in the sidebar
 - Click Add Collaborator and enter your partner's github username
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-- Then `cd` into the project directory
+- Then `cd` into the project directory and type `code .` to open in VSCode
 
 ### Partner 2:
 - After your partner adds you as a collaborator, you'll receive an email to collaborate on the repo
 - Once you've accepted the invite, go to your partner's fork of the repo: https://github.com/YOUR_PARTNERS_NAME/prework-library-loops
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-- Then `cd` into the project directory
+- Then `cd` into the project directory and enter `code .` to open in VSCode
 
 ## Workflow
 - Decide on driver/navigator roles

diff --git a/paring.md b/paring.md
@@ -9,11 +9,13 @@ We'll be working on this practice lab: https://github.com/Guillamoure/prework-li
 - Click the Settings tab, then Manage access in the sidebar
 - Click Add Collaborator and enter your partner's github username
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
+- Then `cd` into the project directory
 
 ### Partner 2:
 - After your partner adds you as a collaborator, you'll receive an email to collaborate on the repo
 - Once you've accepted the invite, go to your partner's fork of the repo: https://github.com/YOUR_PARTNERS_NAME/prework-library-loops
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
+- Then `cd` into the project directory
 
 ## Workflow
 - Decide on driver/navigator roles

diff --git a/paring.md b/paring.md
@@ -2,13 +2,15 @@
 We'll be working on this practice lab: https://github.com/Guillamoure/prework-library-loops
 
 ## Setup
-Partner 1:
+
+### Partner 1:
 - Fork this repo: https://github.com/Guillamoure/prework-library-loops
 - This should take you to a new page on Github for your forked repo: https://github.com/YOUR_NAME/prework-library-loops
 - Click the Settings tab, then Manage access in the sidebar
 - Click Add Collaborator and enter your partner's github username
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
-Partner 2:
+
+### Partner 2:
 - After your partner adds you as a collaborator, you'll receive an email to collaborate on the repo
 - Once you've accepted the invite, go to your partner's fork of the repo: https://github.com/YOUR_PARTNERS_NAME/prework-library-loops
 - Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`

diff --git a/paring.md b/paring.md
@@ -0,0 +1,28 @@
+# How to pair with Github
+We'll be working on this practice lab: https://github.com/Guillamoure/prework-library-loops
+
+## Setup
+Partner 1:
+- Fork this repo: https://github.com/Guillamoure/prework-library-loops
+- This should take you to a new page on Github for your forked repo: https://github.com/YOUR_NAME/prework-library-loops
+- Click the Settings tab, then Manage access in the sidebar
+- Click Add Collaborator and enter your partner's github username
+- Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
+Partner 2:
+- After your partner adds you as a collaborator, you'll receive an email to collaborate on the repo
+- Once you've accepted the invite, go to your partner's fork of the repo: https://github.com/YOUR_PARTNERS_NAME/prework-library-loops
+- Clone the repo: click Clone or Download, copy the link, then in terminal run `git clone <git link>`
+
+## Workflow
+- Decide on driver/navigator roles
+- The driver should share their screen and work on the code from the repo they cloned
+- When it's time to switch roles, the driver should commit their code:
+
+```sh
+$ git add .
+$ git commit -m 'some descriptive commit message'
+$ git push
+```
+
+- Then, the new driver should pull down the new version of the code: `git pull`
+- For now, we're just using one branch for simplicity - in the future, you'll use different branching strategies depending on your workflow
No results found