Looks like to late for comment. Any plain structure with dozens of child of the same rang is hard to maintain, navigate. It is not only about methods in the class. It is about everything. Like UI with 100 buttons. You want to group it. Almost everything can be grouped. So even this CustomerLogic can be decomposed. May be to
CustomerOrderLogic
CustomerAccountLogic. Need real examples.
Never too late! And you are absolutely right, it could be broken even further into more refined classes that only perform one job. I love that you mentioned this point, because I am definitely still learning and appreciate any holes in my knowledge being pointed out.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Looks like to late for comment. Any plain structure with dozens of child of the same rang is hard to maintain, navigate. It is not only about methods in the class. It is about everything. Like UI with 100 buttons. You want to group it. Almost everything can be grouped. So even this CustomerLogic can be decomposed. May be to
CustomerOrderLogic
CustomerAccountLogic. Need real examples.
Never too late! And you are absolutely right, it could be broken even further into more refined classes that only perform one job. I love that you mentioned this point, because I am definitely still learning and appreciate any holes in my knowledge being pointed out.