Mentored Pair Programming
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- content
Research direction
Start with the mentored pair programming guide, then use a scheduling link in the #cyf-pair-programming Slack canvas to arrange a session with a volunteer. Choose a programming task such as a CodeWars kata, explain and plan your approach, write and check the code, and request feedback on specific topics.
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
- Shell
- Stars
- 0
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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-Tools
-
🏕 Priority Mandatory 📅 Sprint 4 Core Module-Tools Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 70/100
CodeYourFuture/Module-Tools#581 ·
-
Install a JDK Open🏕 Priority Mandatory 📅 Sprint 4 Core Module-Tools Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
CodeYourFuture/Module-Tools#480 ·
-
Write a general CV Open🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 4 Core Module-Tools Submit:Slack
Difficulty 2/5 Half a day Newbie friendliness 45/100
CodeYourFuture/Module-Tools#137 ·
-
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 5 Module-Tools Optional Submit:PR
Difficulty 3/5 1-3 hours Newbie friendliness 35/100
CodeYourFuture/Module-Tools#179 ·
-
Prep Exercises Open🏕 Priority Mandatory 📅 Sprint 5 🦑 Size Large Core Module-Tools Submit:PR
Difficulty 3/5 1-2 days Newbie friendliness 65/100
CodeYourFuture/Module-Tools#178 ·
All issues in CodeYourFuture/Module-Tools
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·