Patterns are awesome. With great powers comes great responsibility
Problems
Over Design
Readability
Solutions
Measure the tradeoff of patterns usage.
Create solutions based on real world names (essential) over architecture (accidental).
Choose good names.
Sample Code
Wrong
Right
Detection
It would be very difficult to create automatic detection rules.
A class name with more than one pattern on it, is a warning.
Tags
Abuser
Naming
Conclusion
Chose when to apply a pattern solution. You are not smarter for using too many patterns. You are smart if you choose the right opportunity for everyone.
Relations

Code Smell 06 - Too Clever Programmer
Maxi Contieri ・ Oct 25 '20 ・ 1 min read

Singleton: The Root of all Evil
Maxi Contieri ・ Nov 17 '20 ・ 9 min read
More Info
How to decouple a legacy system
Credits
Photo by Nathan Dumlao on Unsplash
When you have a hammer, every problem looks like a nail.
Discussion (0)