Mentored Pair Programming
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- content, documentation
Research direction
Start with the mentored pair programming guide, then use the scheduling links in the #cyf-pair-programming Slack canvas, or post there if no time is available. Pick a CodeWars kata and complete the session by explaining your thinking, planning, writing code, checking it works, and receiving feedback from the volunteer.
Written by the indexing model from the issue text.
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 for guidance.
Book time with a volunteer using one of the scheduling links in the #cyf-pair-programming Slack channel's canvas. If there are no available times, please post in #cyf-pair-programming.
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.
- Dominant language
- Python
- Stars
- 0
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Complexity
-
NotCoursework
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
🏕 Priority Mandatory 📅 Sprint 2 Core Module-Complexity Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Complexity Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
🏝️ Priority Stretch 📅 Sprint 2 🦑 Size Large Module-Complexity Optional Submit:PR
Difficulty 3/5 Half a day Newbie friendliness 45/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Complexity Submit:PR
Difficulty 2/5 Half a day Newbie friendliness 45/100
All issues in CodeYourFuture/Module-Complexity
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100