Yes, bad names, long methods, mixed level of abstractions for example Sent from my ASUS Eee Pad dimitris chloupis <thekilon@yahoo.co.uk> wrote:

you mean by "unreadable code" , bad choice of naming methods and variables or something more than that , or something else ?

From: Attila Magyar <m.magyar3@gmail.com> To: dimitris chloupis <thekilon@yahoo.co.uk>; A friendly place where any question about pharo is welcome <pharo-users@lists.gforge.inria.fr> Sent: Tuesday, 18 December 2012, 15:46 Subject: Re: [Pharo-users] Nautilius Method Source Pane Coloring

On Tue, Dec 18, 2012 at 10:42 AM, dimitris chloupis <thekilon@yahoo.co.uk> wrote:

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 ru

I think, using comments inside methods and documenting libraries and projects are fairly different topics. I found people often using lots of comments as an excuse for writing unreadable code. But documenting the usage of a library is unarguably important.