Pair program [volunteers only] #11
Description
Trainees, you are assigned many many tickets for pair programming. We do two kinds of pair programming:
- Driver/navigator pairing
- Guided pairing
This ticket is for guided pairing, where the trainee always writes all the code and plans the strategy. There will also be many opportunities for classic driver/navigator pairing, where the driver writes the code and the navigator plans the strategy, but this ticket is helping volunteers practice guided pairing.
Instructions
- Pair up with someone and work on a kata together
- Pairs should explain their thought process, plan out what to do, write the code and check it works
- As a guide, you will need to ask questions to check understanding, provide guidance if they get stuck, give honest and meaningful feedback
🧭 Guidance
- Don't take over! It's important new programmers get used to figuring things out. Provide guidance and assistance but learners need to struggle to overcome obstacles with understanding and technical communication
- Give honest feedback. Trainees can't develop if they don't receive honest feedback about their progress.
- Ask questions. Sometimes asking a clarifying question can help learners discover errors and often promotes more thoughtful responses.
- Encourage best practices. Reinforce good practices like reading error messages carefully sessions and checking documentation.
Why are we doing this?
Pair programming is an excellent way to develop programming and communication skills. It is often much easier to work through something when working on something 1 to 1. It is also helps our trainees to prepare for technical interviews when they'll need to code in front of other people.
Acceptance criteria
- You have pair programmed with at least one person for 30 mins