On Jan 17, 2016, at 9:06 AM, Yuriy Tymchuk <[email protected]> wrote:
That’s the point. Someone finds this disruptive, someone instructing. But it’s
always a true information. So here we are not dealing with the faults of
algorithm but with a way we are communicating a data with a user.
That’s why I kindly ask not to call this things “false positives” :).
I thinks that it makes sense to be bale to disable some critics by their
severity.
Also I think that it’s a good thing to teach beginners to write class comments.
You don’t need special skills for that and making it a habit from the beginning
will payoff in the future.
+1000!
+1 me too.
I remember when Stef introduced the mark on uncomment classes I was against: I
was finding the exclamation mark too disruptive. Then time proved me wrong: is
a nice way to remember people they need to add class comments (and my own
production of comments increased considerably).
;D
I think QA will do the same: it might look disruptive, but is educative in fact.
Yes but you see when this is really first first first class you write in
Pharo....
So I want everybody to have QA on! and to fix them!
And I want more rules I want specific rules for everything every
frameworks but not on the first class a newbie is writing.
People should remember when is the last time they defined a class for
the first time.
I did Python exercises with my son and it was in plain text editor and
it was working.
Stef
