Re: XP and Pair Programming

Ron Jeffries <ronjeffries@xxxxxxx> wrote:

> CLASSICAL REVIEW
>
> CODE BAKED. In the classical review, the code is baked. The
> programmer has completed it, or nearly so. The reviewers (and there
> are often more than one) have not seen the code come into existence:
> they see it statically. They do not understand why it is the way it
> is, and the usual practice in reviews is that the developer does not
> explain how the code got that way.

This can be a plus or a minus. I should be able to figure out your code
without having you there to explain it to me. If I can't, then it's too
complicated, or insufficiently documented. The problem with being
intimately involved with the production of code is that sometimes it's hard
to stand back and see what it looks like with fresh eyes.
.

Relevant Pages

  • Re: XP and Pair Programming
    ... In the classical review, the code is baked. ... >> programmer has completed it, ... and the usual practice in reviews is that the developer does not ... >This can be a plus or a minus. ...
    (comp.object)
  • Re: XP and Pair Programming
    ... In the classical review, the code is baked. ... > programmer has completed it, ... > are often more than one) have not seen the code come into existence: ... Prev by Date: ...
    (comp.object)