On 18 December 2012 10:42, dimitris chloupis <[email protected]> wrote: > ah sorry I missed "worse even". I thought you suggesting that writting long > comments should be counted as negative. > > Also I never asked anybody to start documenting Morphic, I only said I would > prefer if focus was more on documentation than improving existing features. > > Also I dont find that red color thing an importan feature anyway. Though I > do find writting small readable well commented methods extremely important. > If a coder cant figure out what clean code is and why he should do it, I > don't think some red color in the side is going to stop him. > > The problem is that most people start "dirty" with the desire to clean > later, of course they realise that cleaning the code later is actually a lot > of work and never do it. > I did see that happen a lot when I was doing python for blender addons. > Fortunately the situation with pharo is a lot better. > > I am actually considering forcing clean code , with my project . Because I > will be redesigning all those tools of course basing it in the existing > great > work that there is . And was wondering how much a bad idea that is. For > example moving comments outside the method source code using something like > meta tags and forcing the method never to exceed 10 lines. Sound like a bad > idea to me, but still makes me think if there is potential. > > Another example would be not to allow accepting a method if is not > commented. Could annoy some people , but I wonder if there is any real > benefit in the long run. > this mode would be not very nice for quick prototyping.
About the topic: yes, counting the number of AST elements would be better metric for determining whether code "stinks" or not :) -- Best regards, Igor Stasenko.
