First programming lesson: Control structures. Senior developer lesson: avoid them.
Too many decisions together
Violation of Open/Closed Principle.
A new condition should not change the main algorithm.
Create hierarchies/compose objects following Open closed principle.
Use State pattern to model transitions.
Use Strategy Pattern/Method Object to choose for branches.
Since there are valid cases for If/else usages, we should not pull the plug and forbid these instructions. We can put a ratio of if statements/other statements as a warning instead.
How to Get Rid of Annoying IFs Forever
Maxi Contieri ⭐⭐⭐ ・ Nov 9 '20 ・ 5 min read
Photo by Adarsh Kummur on Unsplash
If debugging is the process of removing software bugs, then programming must be the process of putting them in.
Top comments (3)
The code isn't at all different, not sure of the intent here?
If you see the code exactly the same is due to a bug in dev.to cache. Try refreshing the cache
It's been a couple of years and it's definitely the same for me :)