Note: Pair programming did not work well in the Spring of 2011. This will be discussed, and possibly discontinued, during the Fall of 2011. This section (like the entire syllabus) is subject to revision pending discussion as a class.
semester we will do some work with others, and other work individually. You are never discouraged from discussing challenges with other classmates. Likewise, I am always available as a resource. As many of you have engaged in pair programming in previous courses, you know that you are responsible for your own learning. If you are found to be cheating (copying code, etc.), the pain will be immense. Failure is, at that point, only one of the options you'll be facing.
When you are programming as a pair, please consider the following:
Each of you are responsible for every line of code submitted. You earn and lose points as a team, regardless of whether it is for correctness or quality. Keep in mind, this also applies to academic integrity---if your teammate is found to be violating the honor code, you have violated the honor code.
You must both master the course material. In a code walk, you might be asked questions. If you can't demonstrate competency, it may effect your partner. The point of working in a pair is to give you the opportunity to work closely with another computer scientist on interesting problems, and develop a deep understanding of the material covered in this course.
You are discouraged from discussing assignments (in detail) with other pairs. Make an appointment to see me if your pair is stuck.
