This guide highlights concepts related to code review for project assignments. See the Homework Review guide for the eligibility requirements and signup process, which is the same for projects.
TABLE OF CONTENTS
The eligibility requirements and process for signing up for a code review are the same as the Homework Review process. See that guide for details.
For project assignments, there are a few assignment types that involve code review.
These assignments begin after you are passing all of the functionality tests for a project. For example, consider the Project v1.2 Review and Project v1.3 Review assignments.
You earn a grade by signing up for and attending a 1:1 synchronous code review with the instructor. The grade only needs to be requested once.
You are expected to do your own early stage refactoring once you reach the asynchronous review stage. If there is indication you have not, you will be asked to clean up your code and then request another code review. This will count as your one appointment allowed per week. See the “Considerations” section below for what to do before requesting a code review.
These assignments are the final assignment for each project. For example, consider Project v1.4 Design.
These assignments are graded using an asynchronous code review. You will likely need to resubmit this assignment multiple times, undergoing between 1 to 3 asynchronous code reviews to pass.
You signup for an asynchronous code review the same as others, but do not attend a synchronous appointment. ****The calendar appointment system is only used to track the order of code reviews and limit the number of requests per day.
You are still limited to one review per week, even if its asynchronous, unless you are relying on tokens.