[[ Any suggestions on how to best go about code reviews when you have the luxury of everyone
being in the same physical place? ]]
Having done some group review of code or specification, I think that there are two important
points:
- break the document to review into manageable thunk (otherwise the end is rushed)
- have someone in charge to ensure that one particular point doesn't take 90% of the time.
If one point takes too long, it should be put aside with someone in charge to ensure that it
is resolved (a dedicated meeting can be done).