I have found that the more elegant the code is, the harder it is for me to understand what it is trying to accomplish. It is my opinion that "Keep It Simple" wins over elegance. When I have had the urge to get elegant, I make sure I comment the elegance so my less elegant co-workers can figure out what I was trying to accomplish.
Sam Schulenburg James Stroud wrote: > Fredrik Lundh wrote: > > James Stroud wrote: > > > >> See the actual question: > >> > >> >How would you construct a generator to acheive this? > > > > > > if you don't think the context provided by the subject line and the > > sentence before the question is important, how come you're so sure what > > "this" refers to ? > > > > </F> > > > > I'm getting the feeling that "correct" answers have nothing to do with > correctness (i.e. working code) but on some vague notion of "elegance". > Please point me to the page where code elegance is precisely defined so > that I may construct my answers appropriately. And yes, I am too lazy to > google "code elegance". > > James > > -- > James Stroud > UCLA-DOE Institute for Genomics and Proteomics > Box 951570 > Los Angeles, CA 90095 > > http://www.jamesstroud.com/ -- http://mail.python.org/mailman/listinfo/python-list
