Working with a Partner

Looking for a partner? Post in the Search for Teammates thread on Piazza! Please make sure to mark your search as Done once you’ve found a partner. This post on Piazza will open after the start of Project 2.

WARNING: Collaborating with your peers on concepts is a great way to learn. Sharing a solution to any assignment is considerd a violation of acadmic integrity. Unless you are partners (by the guidelines below) you must not show your solution code for any assignment to any other student.

Online Partner Collaboration for Fall 2020

All course activities are purely online for the current semester due to COVID-19. To help with the switch, here are stome tips for remote collaboration for partnerships.

NOTE: The Final Project will have all of the same collaboration and partnership rules and suggestions as Projects 3 and 4.

Useful Technology

Google Meet works well for one-on-one meetings and you can include a link to the meeting in a Google calendar invite.

  1. Go to Google Meet
  2. Select “Start a new meeting”
  3. Copy and send the link under “Meeting ready” on the right to your partner.
  4. Select “Join now”
  5. Use the “Present now” capability to allow both partners to view the code while one person types.

Tips for Effective Online Meeting

Project Partner Norms

Guidelines for Effective Teamwork

NOTE: For the Final Project (which is after Project 4) you must work in groups of four students. Details of the Final Projects are released later in the semester.

Pair Programming

Pair Programming describes a programming technique where all programming work is done by two programmers, working together at a single computer. Within the pair, work is split into two roles, known as the driver and the navigator. The driver is the person at the keyboard, responsible for the actual typing of the code being generated. The navigator is an active observer and monitor of the code being written. The driver and navigator collaborate on all aspects of the software development: design, coding, debugging, etc. They are in constant communication, asking and answering questions of each other. The two programmers may switch roles frequently in the course of a programming session.

NOTE: Working alone? Consider Rubber duck debugging!

Dos and Don’ts

Here are some tips to help clarify.