Codemanships Code Smell Of The Week Inappropriate Intimacy

Summary

When two classes exhibit an unhealthy fascination with each other's bits, we call the 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 ... A key goal of OO design is to minimise depdencies between classes and compknents by packaging data and behaviour as close ... When we see fields that always seem to be used together (e.g., passed together as mathod parameters, or used together in ... Classes that have more than one distinct responsibility (more than one reason to change) violate the Single Responsibility design ... 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 quickly illustrates how to apply the Collapse Heirarchy refactoring to eliminate a lazy subclass Download the ... Jason Gorman refactors a variation of the Message Chains Jason Gorman demonstrates how to reduce the number of method parameters, making them easier to remember and reuse, using ... Quickly following on from the basic example of duplicate