Ok, but it's also the opinion of the GoF, Martin Fowler, Michael Feathers, Bob Martin, Jason Gorman, Kent Beck, Nat Price, Steve Freeman.. etc. Every "good code" book out there will tell you this. I'm not going to ignore all those collective years of development experience, just because I think it is "not bad"Eran wrote:That's like, your opinion, manthis is wrong
Seriously though, you can't say that is "wrong" - it is just different from the way you do it. You'll need to be more elaborate on why you think each simple operation needs its own class as opposed to being a method on a class that binds those operations together.
For one object to have more than one responsibility is possibly the most basic of code smells