Re^2: Tips for managing Perl projects?

I'm confused. First you say that the reviewer should explain what he would have done differently and why, and later you say that he shouldn't.

Comment on Re^2: Tips for managing Perl projects?

Replies are listed 'Best First'.
Re^3: Tips for managing Perl projects? by BrowserUk (Patriarch) on Dec 15, 2004 at 23:30 UTC
Your right. That was ambiguously and contradictively phrased. I've updated in an attempt to clarify, though I'm not sure I've suceeded? Examine what is said, not who speaks. The end of an era! "But you should never overestimate the ingenuity of the sceptics to come up with a counter-argument." -Myles Allen "Think for yourself!" - Abigail "Time is a poor substitute for thought"--theorbtwo "Efficiency is intelligent laziness." -David Dunham "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon	[reply]
Re^4: Tips for managing Perl projects? by itub (Priest) on Dec 15, 2004 at 23:53 UTC
I think it is clear enough now, thanks. I would say that the idea is not to turn the review into a debate.	[reply]


No such thing as a small change
	PerlMonks