Add extra guidance on mentored pair programming

org-cyf-guides/content/pair-programming/_index.md

@@ -0,0 +1,19 @@
++++
+title = 'Pair programming'
+description = 'Practice writing code and getting support'
+emoji = '👥'
++++
+
+Pair programming is an excellent way to develop programming and communication skills.
+
+It is often much easier to work through a problem when working with someone 1-to-1.
+
+It also helps our trainees to prepare for technical interviews when they'll need to code in front of other people.
+
+## What
+
+Pair programming is working together with someone else to code a solution to a problem.
+
+Pick a piece of programming to do, find a buddy, and work on it together.
+
+Sometimes one person does all of the writing, and has discussion with the other. Other times, people take turns writing.

org-cyf-guides/content/pair-programming/index.md → org-cyf-guides/content/pair-programming/guidance/index.md

@@ -1,30 +1,19 @@
 +++
-title = 'Pair programming'
+title = 'Guidance'
 description = 'Practice writing code and getting support'
 emoji = '👥'
+weight = 1
 +++
 
-Pair programming is an excellent way to develop programming and communication skills.
+## How
 
-It is often much easier to work through something when working on something 1-to-1.
+You can do pair programming in person (sharing one computer), or remotely (either by sharing your screen, or using something like [CodeTogether](https://marketplace.visualstudio.com/items?itemName=genuitecllc.codetogether)).
 
-It is also helps our trainees to prepare for technical interviews when they'll need to code in front of other people.
-
-## What
-
-Pair programming is working together with someone else to code a solution to a problem.
-
-Pick a piece of programming to do, find a buddy, and work on it together.
-
-You can do this in person (sharing one computer), or remotely (either by sharing your screen, or using something like [CodeTogether](https://marketplace.visualstudio.com/items?itemName=genuitecllc.codetogether)).
-
-Sometimes one person does all of the writing, and has discussion with the other. Other times, people take turns writing.
-
-## Guidance for trainees
+## Guidance for learners
 
 When approaching a problem, you need to **explain your thought process**, **plan out what to do**, **write the code**, and **check that it works**.
 
-## Guidance for volunteers
+## Guidance for mentors
 
 **Help people learn**: Most of the exercises the trainees are doing aren't useful in their own right. The point is for the trainee to learn and grow through them. Focus on understanding, and techniques that will help solve the next problem.
 

org-cyf-guides/content/pair-programming/mentored/index.md

@@ -0,0 +1,28 @@
++++
+title = 'Mentored pair programming'
+description = 'Practice writing code and getting support'
+emoji = '👥'
+weight = 2
++++
+
+We assign **mentored pair programming** as a coursework assignment throughout the course.
+
+All of the standard [pair programming guidance](../guidance) applies - make sure you're familiar with it.
+
+**Before** a mentored pair programming session, learners should decide what they're going to pair on and share this with the volunteer, e.g. by sharing a link to a particular Codewars exercise, a particular piece of coursework, or some other problem.
+
+**During** mentored pair programming, the **learner** should:
+* Explain their throught process
+* Break down the problem
+* Plan what code to write
+* Write all of the code
+* Check that it works
+
+The **mentor** should:
+* **Ask questions** to get the trainee thinking. It's always better to ask than tell.
+* Help the trainee think about breaking down the problem
+* Support the trainee as they write code
+* Help the trainee to debug their code
+* Stretch the trainee by bringing up extra concerns
+
+This is different from other forms of pair programming, where both people may be expected to write code, or people may take turns at different roles. This is because the goal is different - the goal is teaching.