March 22

Open discussion of code review : what is the best way for us to do this over the next week?

Proposal:

• I'll set up a "Code Review" page with a link to a "review" page for each person.
• I'll also add some generic starting questions there.
• "Code Review" page and each review page group viewable and editable.
• Comments signed, not anonymous.
• Each review page would be free format - multiple reviewers possible.
• Feedback on each review posted to same page, also group viewable.

Your thoughts?

I'd like to set a due date of next week, March 29 for the round of constructive comments and the feedback about how useful those comments were. Then perhaps a discussion in class about the process and impressions rather than any specific person's work.

coming next

Next status update: midterm update, due after the midterm break, April 12. (It would be great to have something tangible by that point.)

asides

• code smell
• code style
• documentation vs comments
• Ask HN: Codebases with great, easy to read code?
• Why don't you use ... | hackernews discussion