[bip] Writing Code that Doesn't Suck

Christopher Lee leec at chem.ucla.edu
Mon Sep 24 20:59:54 PDT 2007


All good points.  I'd like to suggest another consideration: code  
review.  All code tends to gradually accumulate a certain level of  
cruft, unless there is an active process vacuuming it out regularly.   
Occasional refactoring is only a partial answer, in that it tends to  
focus on specific high-level problems, rather than vacuuming up cruft  
everywhere.  Getting smart outsiders to look at your code is probably  
the most valuable way to get a different set of perspectives, and  
figure out what needs cleaning up.  Agreeing to code review is one  
way that developers can demonstrate a commitment to "code that  
doesn't suck".

In this spirit, I would like to volunteer Pygr for a code review by  
people within this group, once the 0.7 release is finalized.  This  
clearly would have benefit for Pygr, and hopefully it would also have  
benefit for people in this group (i.e. the result would be better  
software).  We may want to start with just one piece of the code.  If  
people are willing to participate in such a code review, please reply  
to this mailing list...



More information about the biology-in-python mailing list