Why?

How?

Handbook is the standard baseline for all of our code
- Everyone can contribute to the handbook if/when things change or new points are decided upon
Reviewer: Constructive, helpful criticism only
- Ask questions rather than make statements. A less-optimal decision is often made due to time constraints.
- Give kudos to GOOD code!
Reviewee: Take criticism well, provide counter-arguments when appropriate

FYI: Nice-to-know tips that don’t warrant a rewrite but should be implemented in future projects
Low Priority: Should fix, whenever time permits in a future round of revisions
Medium Priority: Needs to fix, as soon as possible
High Priority: Must fix, now!
Reviewer does not implement fixes, only the
project’s developer