Correct code/unit testing (was Re: Efficient python programmi ng...)
Delaney, Timothy
tdelaney at avaya.com
Tue Jun 11 00:32:33 EDT 2002
More information about the Python-list mailing list
Tue Jun 11 00:32:33 EDT 2002
- Previous message (by thread): Correct code/unit testing (was Re: Efficient python programming...)
- Next message (by thread): Correct code/unit testing (was Re: Efficient python programming...)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> From: Peter Hansen [mailto:peter at engcorp.com] > > Kragen Sitaker wrote: > > > > Peter Hansen <peter at engcorp.com> writes: > > > Have you never spent a large amount of time carefully > > > designing and coding a wonder little program, and checked it over > > > very carefully, even with a peer, and later found a bug in it? > > > > Of course! People are fallible, it's much easier to do a bad code > > review than a good one. > > I have to confess I have never seen a successful code review, nor > an environment in which they were used regularly and which had a > high level of code quality. Clearly as a result I'm fairly biased > against them -- I should keep a more open mind on the issue perhaps. I presume you mean a full, formal review by a group for a large piece of code? I'm certain that with your experience with XP, you have seen and taken part in *many* successful reviews (where success means the code is improved as a result). Tim Delaney
- Previous message (by thread): Correct code/unit testing (was Re: Efficient python programming...)
- Next message (by thread): Correct code/unit testing (was Re: Efficient python programming...)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list