Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ukma!uflorida!indri!nic.MR.NET!umn-cs!klein!meuer
From: meuer@klein (Mark Meuer)
Newsgroups: comp.software-eng
Subject: Re: code reviews
Message-ID: <13716@umn-cs.CS.UMN.EDU>
Date: 19 Jun 89 14:27:04 GMT
References: <12047@bloom-beacon.MIT.EDU> <116@opel.UUCP>
Sender: news@umn-cs.CS.UMN.EDU
Reply-To: meuer@klein.UUCP (Mark Meuer)
Organization: Minnesota Supercomputer Institute
Lines: 19

In article <116@opel.UUCP> johnk@opel.UUCP (John Kennedy) writes:
>
>I can't help but chuckle when I see code reviews and productivity in the
>same paragraph.  It's good for the project, it's what the customer wants,
>but be assured that it's an increase in overhead and a decrease in productivity.
>
>I wish this weren't true.
>
>John

I beg to differ.  I used to work for a software company where peer
reviews were used extensively.  They were very helpful in a number of
respects, and were well worth the effort.

It is true that reviews add overhead to the development, but that time
is made up for by better designs and much better communication and
understanding between members of the programming team.

-mark