CodeYourFuture / CodeYourFuture/Module-Logic
Mentored Pair Programming
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Learning Objectives
- [ ] Talk aloud when thinking about a problem.
- [ ] Write code in front of someone else.
- [ ] Analyse your strategies for solving problems in code.
### 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 you to prepare for technical interviews when you may need to code in front of other people or explain your solution to a problem.
Pick one piece of programming you're doing (we recommend a CodeWars kata) and pair up with a volunteer to work on it together.
See [the mentored pair programming guide](https://programming.codeyourfuture.io/guides/pair-programming/) for guidance.
Book time with a volunteer using one of the scheduling links in the [#cyf-pair-programming](https://codeyourfutur-yov6609.slack.com/archives/C07PA66MQMC) Slack channel's [canvas](https://codeyourfutur-yov6609.slack.com/canvas/C07PA66MQMC). If there are no available times, please post in [#cyf-pair-programming](https://codeyourfutur-yov6609.slack.com/archives/C07PA66MQMC).
Remember, as a learner, you will need to **explain** your thought process, **plan** out what to do, **write** the code and **check** it works.
### Submission & Review
You will get feedback from the volunteer during the session. If there are specific topics you would like to receive feedback on then let them know at the start of the session so they know what to focus on.
Contributor guide
Research direction
Start with the mentored pair programming guide linked in the issue, then review the scheduling options in the #cyf-pair-programming Slack channel. The stated outcome is to complete one programming exercise with a volunteer, explain the approach, write and check the code, and receive feedback.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100