One Responsibility per Method
The design becomes clearer by refactoring a class so that each method has only one responsibility.
Methods must have a single responsibility, like classes because it makes them easy to reuse and change. Small methods help to improve the design by making it easier to rearrange behavior. Refactor your code even if the ultimate design is unclear because refactoring helps to clarify the design. Principles exist to establish a common ground for the whole code base. Each class should be responsible for achieving maintainable and flexible object-oriented software.
A community of professionals means that we are expected to share and learn with each other, raising the bar of our industry.
Professionals are defined by the way they work. Sound practices are good until we discover better ones to replace them. Experimenting becomes very costly when the software is not modular and testable. It is crucial to perform Refactorings even if you are still determining the ultimate design. This is because good practices can help reveal the design, especially when it is not straightforward. Having each method serve a single purpose makes what the class does more evident.
Refactoring is the most transparent path toward increasing flexibility in any software system.
