Well, as others say: "It was hard to write, it should be hard to read." ;) But i only write comments above methods/functions or on places that are definitely not self-explanatory (such as counting from 1 instead of 0). But maybe i should write more comments (thinking stuff like "what the hell was I thinking when i coded this piece of crap?" does happen sometimes). Michiel Kenny Billiau wrote:

http://blogs.wsj.com/biztech/2008/06/06/men-write-code-from-mars-women-write...

I know how I write, and I like to make the code 'clever'. I don't really know what I mean by clever, because I seem to experience it as a feeling (ah, is this the testosteron high?). But I do group lines of code together with comments, unless

1/ its meaning is too obvious or 2/ when things are too experimental (why describe what you when you don't really know where you're taking yourself) or 3/ when it's the same old thing over and over again or 4/ because the code itself is selfexplanatory (foreach ($genes as $gene) will probably loop over an array of genes, no?)

So, do you the same?

-- ================================================================== Michiel Van Bel PhD student Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM mibel@psb.ugent.be http://www.psb.ugent.be ==================================================================