|
Mark S. Waterbury wrote:
IMHO, what is far more important than a "code review" is to do a "design review" to ensure the requirements are well understood, and then review the proposed design to ensure it will meet those requirements, BEFORE any code is ever written.
Both are equally important, imho. The audience for each is different though ... Design review s should be done with the user community (or their representatives). Code reviews are done with developers. I would also throw into the mix a Technical Design Review ... to evaluate the implementation plan. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.