Code Smell 63 - Feature Envy
If your method is jealous and don't trust in delegation you should start to do it.
Bad Responsibilities Assignment
- Move method to the appropriate class.
Some linters can detect a sequential pattern of collaborations with another object.
- We should assign responsibilities according to real object mappers and avoid abusing other objects protocol.
We argue that design practices which take a data-driven approach fail to maximize encapsulation because they focus too quickly on the implementation of objects. We propose an alternative object-oriented design method which takes a responsibility-driven approach.
This article is part of the CodeSmell Series.
Great advice Maxi 👏
The job instance knows its properties, so by moving the print responsibility close to their source of change; we make the candidate class depend on one point of change rather than multiples attributes in the job class 👌