Don't make two or more things at once.
TL;DR: Try to be as atomic as possible in your methods
-
Coupled Code
-
Harder to test
-
Harder to read
- Break the method
Refactoring 002 - Extract Method
If you name a method with 'And' you are probably missing an extract-and-break method opportunity.
calculatePrimeFactorsRemoveDuplicatesAndPrintThem()
// Three responsibilities
calculatePrimeFactors();
removeDuplicates();
printNumbers();
// Three different methods
// You can test them and reuse them
[X] Semi-Automatic
Some linters can warn us about methods including the term 'and'.
- Coupling
When making methods, it is very important to play some rubber duck story and tell ourselves if we are making things right.
Code Smells are just my opinion.
Photo by Scott Sanker on Unsplash
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
Joshua Bloch
Software Engineering Great Quotes
This article is part of the CodeSmell Series.