Re^2: How should I do (and document) effective semi-formal code review?

(you have specs, right?)

But of course. ;-)

Thank you much for the input. I'd not thought of the review as a meeting.

<–radiant.matrix–>
Ramblings and references
“A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort.” — Herm Albright
I haven't found a problem yet that can't be solved by a well-placed trebuchet

Comment on Re^2: How should I do (and document) effective semi-formal code review?


Come for the quick hacks, stay for the epiphanies.
	PerlMonks