Object Calisthenics

[LukeTrynchuk]

Refactor code to strictly adhere to Object Calisthenics.

[LukeTrynchuk]

I have chosen to Omit the All primitives wrapped in a class and no more than two data member rules. After implementing in one my classes, I have found that, while the rules may be appropriate for Software Development, it I found it to be rigid for game development. While Software is clearly defined before development, games are constantly changing design, even if well planned out. By implementing such rules, It creates a rigid approach to designing data in classes.

I found that :

• It became difficult to redesign the class if any changes were to happen to the data members.
• It encouraged bad naming due to the fact that data sets often were arbitrarily paired to keep to the 2 data members per class rule.
• It also made the getter / setter rule difficult to follow because of the fact that certain encapsulated objects may rely on other encapsulated object data to perform actions. In doing so, you may need to redesign the data setup and therefore run into the rigid nature of 2 data member per class.

Despite these short comings :

• Classes should still follow the one dot rule, small classes and possibly encapsulated collections.
• No more than 10 data members (may change but a large amount of data members may point to a class that is doing too much).
• If testing is concerned, follow the Humble Object pattern.