Practice What You Learned
Pair and Group Programming
During this class you will be expected to practice both Pair and Group Programming, this is a part of the class experience and is imperative that everyone buy in and take part in the process.
You can read this article about why we practice pair programming. This is, of course, valuable for teaching, but it is also the standard at many top tech companies.
You don't normally sit by yourself in a room coding in a vaccuum! You are part of a team trying to solve problems together.
When you want something done well, it is almost always better to find a good team than hire a single individual.
Your Job
Sometimes throughout the course you will be put in breakout rooms of either a pair or a group.
When in a Pair
- One student will be what is called the "driver" and one student will be the "navigator."
- The navigator talks to the driver, but never types. They direct the driver where to go (like GPS).
- The driver follows the instructions of the navigator, and may give feedback, but whoever is the navigator is currently running the show.
- No one should always be navigator or driver; switch it up occasionally.
- The driver should be sharing their screen.
When in a Group
- One person should be sharing their screen and the team should collaborate, like you would at a corporate meeting.
- The person sharing their screen should act as the "recorder" and take the meeting's minutes.
- Everyone should be communicating at all times.
- Once the breakout room closes, whoever was recording should share what they recorded with the entire group.
What is Not Permissable
- It is not ok to go into your breakout room, turn your camera off, and not interact with the class.
- It is not ok to go into your breakout room and do work that was previously assigned, instead of what the breakout room is working on.
- It is not ok to speak over other students in the breakout room.
- It is not ok to give solutions to problems in the breakout room without an explanation.
- It is not ok to Google the direct answers to problems, as opposed to doing the proper research via MDN, W3C, ECMAScript docs etc.
Tips
- If you are not using documentation in breakout rooms, you are not going to find the answers.
- If you are not reviewing the class material, you are not going to find the answers.
- If you are not using the written bonus texts in the breakout rooms, you are not going to find the texts.
- If you are not working together, you are not going to find the answers.
Activity
- Select a problem from last night's homework.
- Use the pair/group/team programming priciples above and work through the problem together.