CodeYourFuture / CodeYourFuture/Module-Complexity
Mentored Pair Programming
- Linguagem predominante
- Python
- Estrelas
- 0
- Forks
- 60
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
### 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.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
Comece pelo guia de programação em pares com mentoria e, em seguida, use os links de agendamento no #cyf-pair-programming Slack canvas ou publique lá caso não haja nenhum horário disponível. Escolha um kata do CodeWars e conclua a sessão explicando seu raciocínio, fazendo o planejamento, escrevendo o código, verificando se ele funciona e recebendo feedback da pessoa voluntária.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Domínio
- content, documentation
- Tipo de issue
- Documentação
- Dificuldade
- 1/5
- Tempo estimado
- 1-3 horas
- Status de atividade
- Pouca atividade
- Clareza
- Claramente especificada
- Facilidade para iniciantes
- 72/100