CodeYourFuture / CodeYourFuture/Module-Legacy-Code

Mentored Pair Programming

オープン
#236 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
🏝️ Priority Stretch 📅 Sprint 1 Module-Legacy-Code Optional Submit:None
主要言語
JavaScript
スター
0
フォーク
77
PR マージ指標
30日以内にマージされた PR はありません

説明

### 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.

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

Read the linked mentored pair programming guide first, then choose a programming task such as a CodeWars kata. Book a session through the #cyf-pair-programming Slack canvas, or ask in the channel if no times are available; done means completing the session, explaining your process, writing and checking the code, and receiving feedback.

索引モデルが issue の本文から書いたものです。

評価

領域
documentation
issue の種類
ドキュメント
難易度
1/5
見積もり時間
1〜3時間
活発さ
静か
明瞭さ
明確に書かれている
初心者へのやさしさ
35/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。