On 2009-11-10, at 7:40 AM, Stéphane Ducasse wrote: > if you want to have fun try to identify the number of times certain > parts are duplicated inside the same method. > > Stef
Actually an interesting exercise here would be to determine who originally wrote the method, then decide is it a result of the author's original coding, or the result of 10 people hacking it. If it's mostly the result of a single author, then I'm sure some nifty tool (someone could write) could determine which other methods the person authored then kick out the more complex ones and decide if the same coding practises are followed, er then mark them as candidates for simplification? I mention this because it reminded me of a project I was on years ago where after a consultant had left we determined his code was problematic based on bug reports statistics and at 2:00 am one morning I and the senior project leader pressed *delete* on all that code base since we had decided it was cheaper to rewrite it all from scratch versus fixing it. -- = = = ======================================================================== John M. McIntosh <john...@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
