kilon wrote
EVERY method needs a comment , not because its that hard to read a few lines of code but because its plain simpler and faster.
-100. Prime example: AbstractBindings>>#initialize "Initialization code for AbstractHolder" That comment is totally redundant for everyone but novices (and maybe even for them). It's actually worse than that: a) I have to read it to find out it's a totally useless comment b) As you can see, it's already rotted. The class is called AbstractBindings, but the comment thinks it's AbstractHolder So, I agree that there may be a "why" in many cases that would be great to capture in a comment, it does not apply to *all* cases. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Small-Methods-dont-need-comments-true-or-myt... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.