Codemanships Code Smell Of The Week Message Chains

Summary

Jason Gorman refactors a variation of the Classes that have more than one distinct responsibility (more than one reason to change) violate the Single Responsibility design ... Lazy classes add little value for the maintanance burden they incur. In this example, Jason Gorman illustrates how to safely inline ... When a method on one class develops an unhealthy fascination with the features of one of its collaborators, this creates ... When two classes exhibit an unhealthy fascination with each other's bits, we call the Inappropriate Intimacy. It's essentially ... Many people have been brought up to see comments as a good thing, but experience has taught us that in reality not only are ... Jason Gorman demonstrates how to reduce the number of method parameters, making them easier to remember and reuse, using ... Again with the multiple responsibilities and the Account refactoring, but this time the responsibilties are completely and cleanly ... Switch statements are bad from an OO design standpoint. Not only because they're basically big nested IF statements, but ... When we see fields that always seem to be used together (e.g., passed together as mathod parameters, or used together in ... A key goal of OO design is to minimise depdencies between classes and compknents by packaging data and behaviour as close ... Jason Gorman quickly illustrates how to apply the Collapse Heirarchy refactoring to eliminate a lazy subclass Download the ...