Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link info about partners #66

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Link info about partners #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ORIENTACIÓN-es.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Saber escribir codigo es solo un aspecto de ser un dev profesional. Otro aspecto

Una parte de tus horas cada semana estaras [programando con tu pareja de equipo](https://www.microverse.org/blog/how-remote-pair-programming-works-and-why-it-can-change-your-life) - aqui es donde la colaboración más magica ocurre.

Programar en pares trae unas oportunidades muy emocionantes de enseñar y aprender de tu pareja, ver otra perspectiva y/o visión de los retos que estan enfrentando y avanzar en las metas compartidas.
Programar en pares trae unas oportunidades muy emocionantes de enseñar y aprender de [tu pareja](PROJECT-BRIEF.md), ver otra perspectiva y/o visión de los retos que estan enfrentando y avanzar en las metas compartidas.

No hay una sola manera de programar en pares, pero en general te encuentras con tu pareja por Zoom y trabajaran la historia de usuario o tarea de la semana. Animate a probar maneras distintas de programar juntxs para ver que les va mejor acorde a sus estilos de colaboración.

Expand Down Expand Up @@ -137,7 +137,7 @@ Eso fue demasiado, ¿Cierto? Es muy probable (💯%) que hayamos olvidado u omit
- Trabajaremos juntos por 8 semanas para construir un Smart Shopping List. Puedes ver un demo de lo que otros equipos construyeron [aquí](https://www.youtube.com/watch?v=uWgkwY_VBPo&feature=youtu.be)
- Los equipos están conformados por 4 developers, 2 mentores y un mentor asistente.
- Cada semana, los equipos de developers se separarán en 2 parejas. Cada pareja trabajará un issue del project board en el repositorio de Github del proyecto.
- Los developers invertirán 5 horas por semana para trabajar en el proyecto. Esas horas incluyen: Pair programming con su pareja semanal, investigación, trabajo con su pareja de manera asíncrona en su issue, creación de Pull Requests y code reviews.
- Los developers invertirán 5 horas por semana para trabajar en el proyecto. Esas horas incluyen: Pair programming con [su pareja](PROJECT-BRIEF.md) semanal, investigación, trabajo con su pareja de manera asíncrona en su issue, creación de Pull Requests y code reviews.
- Cada domingo durante el programa, el equipo tendrá un Weekly Sync donde los developers demostrarán el feature que construyeron durante la semana y un mentor liderará un learning module o el equipo participará en el Retrospective.

## ¿Qué sigue?
Expand Down
4 changes: 2 additions & 2 deletions ORIENTATION-en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Knowing how to code is just one aspect of being a professional web developer. An

### Pair Programming:

A portion of your dedicated hours each week will be spent [pair programming](https://www.microverse.org/blog/how-remote-pair-programming-works-and-why-it-can-change-your-life) with your partner for the week—this is where the most magical collaboration happens.
A portion of your dedicated hours each week will be spent [pair programming](https://www.microverse.org/blog/how-remote-pair-programming-works-and-why-it-can-change-your-life) with [your partner for the week](PROJECT-BRIEF.md)—this is where the most magical collaboration happens.

Pair programming offers some really exciting opportunities to teach/learn from your partner, get a different perspective and/or insight on the issues you’re facing, and drive forward progress on your goals.

Expand Down Expand Up @@ -130,7 +130,7 @@ Whew, that was a lot, right? There’s a good chance (💯%) we’re forgetting
- We will spend 8 weeks working together to build a smart shopping list app. See a demo of the same app that a previous team built [here](https://www.youtube.com/watch?v=uWgkwY_VBPo&feature=youtu.be).
- Collab Lab teams consist of 4 developers and 3 mentors.
- Each week, the team’s developers will break up into 2 pairs. Each pair will tackle a single issue from the project board in the team’s GitHub repo.
- Developers will each spend about 5 hours per week working on the project. These hours include pair programming with weekly partners, researching, working with partner asynchronously on issues, creating pull requests, and doing code reviews.
- Developers will each spend about 5 hours per week working on the project. These hours include pair programming with [weekly partners](PROJECT-BRIEF.md), researching, working with partner asynchronously on issues, creating pull requests, and doing code reviews.
- Each weekend during the program, the team will have a Weekly Sync where developers will demo the feature they built in the previous week and a mentor will lead a learning module or the team participate in a retrospective.

## What's Next?
Expand Down