We'll discuss the code reviews in class on Monday, September 27. In brief, code reviews tend to be somewhat stressful for the person being reviewed, so we all need to take steps to make the process collegial and constructive. We need to point out what's good in each other's code, as well as providing some ideas on where to make some improvements.
In preparation for your code review, please do the following.
Write comments for each of the programs in your group (including your own). Assemble all your comments for all the programs into a single document (probably 1-2 pages), and bring enough printouts of your document to give each person, including Jeff, a copy. Your comments don't have to be polished, but they should be polite and constructive. For guidance on what constitute polite and constructive comments, consult the golden rule. That is, think about what kinds of feedback you will be happy to receive if your goal is to improve your programming skill.
Specifically, for each program:
Based on the feedback you receive at your code review, you will revise your program and hand it in again by class time next Wednesday, the 27th. Please submit it in a folder called loganalyzerrevision.
Your grade for the loganalyzer assignment will be based on the quality of your revised program, the quality of your participation in the code review, and by your responsiveness in the revision to the feedback you received at the code review.