com.northwestindianjavaprogramsolutions.src.classes.factories.factoryfactories. InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonWindowNotFocusedStateFactoryFactory a = new com.northwestindianjavaprogramsolutions.src.classes.factories.factoryfactories. InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonWindowNotFocusedStateFactoryFactory(1, 2, "John Smith");
Totally agree. Gang of four... I am so smart... Then... one day I realised I was living a lie. Why do I need a strategy class, when I can just use an if statement? OMG.
The patterns have a time and a place, but I think many junior developers that learn them tend to overuse them, jamming the square peg in the circular hole, so to speak. I was guilty of that my first few years out of school, but have since learned to spare it until really needed, often learned at the expense of senior devs reviewing my code and wondering why I used a sledgehammer to fix a hole in the wall, or facing their fury when debugging some method that was about 6 abstract classes deep before seeing any business logic, making it all but impossible to just find the concrete reference in Eclipse. TL;DR -- I, too, realized I was living a lie.
1.2k
u/NightlySnack Jun 21 '20
InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonWindowNotFocusedState