Timeline for What if I will not use Software Design Patterns?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2013 at 13:35 | comment | added | kdgregory | +1 for the comparison to physical structures. I would add that it helps to build a house if you already know that a "truss" is a good structure to support the load of a roof, rather than experimenting and hoping that it doesn't collapse. | |
| Nov 29, 2013 at 4:20 | comment | added | Matt D | And this sums up exactly my views on patterns. They're wonderful tools for communicating what you're doing with other people. You never build them exactly though because every problem is different. But they're a gist, a direction, and a rough set of guidelines to follow, and it makes it easy to explain to others what the heck you're doing. | |
| Nov 28, 2013 at 17:22 | comment | added | Binary Worrier | ... Learning about design patterns, and learning how to use them correctly saves you so much time, you're less likely to try reinventing the wheel, stops you from leading yourself down a road towards bad design and building bad solutions. Suck it up and learn the patterns, use them when they work for you, and don't use them when they won't. | |
| Nov 28, 2013 at 17:20 | comment | added | Binary Worrier | +1: Absolutely right. I started OO development before design patterns became known or popular. Yes we also invented things like factories, singletons and something that, when you squinted at it in a bright light sort of looks like the Strategy pattern. The point is now that I know design patterns I know the the factories were OK but could have been done better, the Singletons were badly done and what might have been a Strategy pattern would have been much better if it actually had been a Strategy pattern. | |
| Nov 28, 2013 at 17:03 | history | answered | Telastyn | CC BY-SA 3.0 |