Class Discussions

Students will be expected to actively participate during class and to meaningfully contribute to class discussions. In general, students should volunteer such participation (but may be involuntarily volunteered). As a part of this participation, students will need to attend every class and lab session for the course. Not being present for any graded component of the class yields a score of 0 for that component automatically. Students will be graded not merely on the existence of their contributions to class discussions but also on the quality of said contributions.

In order to make sure the appropriate students get credit for their contributions, every student should make a paper nameplate with their name clearly printed. Students should bring these to class. Contributions by students without nameplates may or may not be counted. Instructions for creating such a nameplate can be found here.

Code Review Fridays

One form of participation, both individual and group, will be in class code reviews. Each group will submit 150-200 lines of code from their term project via CourSys by Wednesday at 10PM each week. I will curate the submissions and make one or two chunks of code available to the class. You should review the code before class on Friday. We will then review and discuss the code on Friday of each week in order to consider trade offs made in the code, risks present, and how the code might be improved. Note that I reserve the right to select any code from the term projects (or other sources); however, this gives groups the opportunity to select code that they found thorny or particularly displeasing to write.

The code that each group submits should compile and run. It does not to be entirely correct for all inputs, but it should be clear that the group has at least tried to execute the code. Design prototypes that provide executable scaffolding for project features are fine.

Code review Fridays will start after the first week of labs.