Hi guys I would like to have mindset revolution. I would like that Pharo HELPS us to produce good code and not just PUNISH us when we do mistakes. Let me show you an example. I write a little method and as a good and nice programmer I place my little utility method in the utilities protocol. I commit and then I get a FAILED ERROR RED BAR telling that I’m an asshole because I did not place that &*T^(^&(* method in utils. Something that Cop stuff is not even able to tell me precisely what is the problem There is a method in class X that use an undefined instance variables. I always thought that computers were about doing clever stuff… but the Cop inside Pharo proves me the inverse. I wonder why instead of investing in stupid rule we do not invest in building simple tool that do the job for us. Why the system cannot recategorise the method for me. Why the system does not remove the unused variable automatically prompting before I commit. Oh my dear Stéphane I saw that you left this horrible unused instance variable, do you want me to clean for you? Yes be my guest. This is why I invested by improving the automatic categorizer. This is why I did a tool to analyse the frequency of methods in terms of their protocol and you can ask the tool please fix all badly categorized methods. https://github.com/Ducasse/MethodCategorizer/blob/master/MethodCategorizer/ProtocolFinder.class.st This is always why I HATE all these %^&*^&(&*^&*(%^(& warnings that get into my way when the system could fix them for me in no time. SO THIS IS A CALL FOR A CHANGE OF PARADIGM Can Pharo help me in my development instead of bitting me? Can we STOP adding more and more dull rules and produce something that HELP US? https://github.com/Ducasse/MethodCategorizer/blob/master/MethodCategorizer/ProtocolFinder.class.st THIS IS NOT BECAUSE WE HAVE A HAMMER THAT WE SHOULD NAIL EVERYTHING. THIS IS OUR DUTY TO INVENT NEW TOOLS AND NEW WAYS TO HELP DEVELOPERS! S.