Code Review Procedure

CS 133JS, Beginning Programming: JavaScript

Contents

Overview

Each student is on a team with one or two other students who are their lab partners. On Moodle, each team of lab partners is listed with a team name: Alders, Birches, Cedars, etc.

There are three versions of each lab assignment—versions A, B and C. Each lab partner will do a different version. This allows each student to look at the other’s work and give them feedback without seeing a solution to their own assignment.

Instructions

Giving and Getting a Code Review

When a student has a beta (draft) version of their lab assignment ready, they will post it in team’s Discord channel. This should be done before the due date for the beta version.

A lab partner will the review the beta version using the code review form provided by the instructor and put yes or no in the "beta" column for each question on the form. This should be done before the due date for the code review. Each lab partner will do one review in “round robin” order: student A reviews B, student B reviews C, and student C reviews A.

What to Do with the Code Review You Give

Post the code review for your lab partner in your Discord team channel and submit the review using the Lab Review assignment link on Moodle.

What to Do with the Code Review You Get

After getting a code review, you may revise your lab work. Fill in the right-most column (“production”) of the review form to indicate any revisions. Fill in the right-most column completely, even if you didn’t change anything. Then, upload the final (aka production) version of your lab work to Moodle and the completed code review of your own lab work.

What to Do If Something Goes Wrong

FAQ

 


By Brian Bird, Lane Community College. Written winter 2016. Revised fall 2025