Does anyone else think some of the Sonar rules are actually crap?

In particular the Put all you variables above methods one?

I have some static methods and variables and some object ones.

Apart from creating a new class for them which I think is over kill for just a few helper methods, don't you feel you should keep all static stuff separate?

Clean code shouldn't be about following arbitrary debatable rules, it should be preventing the horrible crap that any experienced developer would instantly call shit... If he didn't write it.

And I'm pretty sure I'm experienced so if I'm not calling a price of code shit...I don't see why Sonar should...

  • 0
    As long as your team is consistent about placement, I couldn't give a shit where you put stuff. So why not just utilise an automated check for it?
Add Comment