Re: Will you help me put together a code review checklist?
On Nov 21, 8:37 am, Mark P <email.powe...@gmail.com> wrote:
On Nov 15, 3:16 pm, James Kanze <james.ka...@gmail.com> wrote:
On Nov 15, 12:25 am, Francis Glassborow
Almost all of the projects I've seen are large enough that no
one person could possibly keep everything in their head at one
time. The correct answer here is proper documentation, so all
members of the team can quickly find the information they need,
when they need it.
In my experience, the ability to execute a reviewers unit test and
(perhaps) compare results provides a lot of value added.
I'm not sure what you're arguing for. That reviewers should
write unit tests? Instead of or in addition to the original
programmer? My experience has been that the best results come
from having the unit tests as part of the code being reviewing.
In particular, a code unit can fail review because its unit
tests aren't exhaustive enough.
My company has a limit on the size of the word product but we
often miss things and I think we have 'proper documentation'.
I'm not sure what you mean by "the word product". But part of
the motivation of code review is to ensure that a programmer
reading the code and the available documentation can understand
the code without problems. If he can't, it fails the review.
--
James Kanze
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]