Re: Code reviews

David,

I agree that code reviews and technical design reviews are a good thing
but most of the System i shops I've worked in over the years have been and
continue to be one-man operations and the programmers have come more from
business backgrounds rather than computer science backgrounds. I think my
experience isn't that far out of the norm and this might explain a lot when
it comes to employing formal development methods vs. just getting the job
done. This is also one of the reasons I appreciate the expertise this list
and other online/print resources provide.

Kind  regards,

BJ


On 12/15/06, David Gibbs <david@xxxxxxxxxxxx> wrote:

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

--
Check out the System i Search Engine: http://search.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.