I definitely agree with that. I was one of those junior developers who picked up that book. All I could see were the patterns. What newbie wouldn't want to say, "I created a new Singleton Abstract Factory." ?!? It seemed as if Patterns started sprouting from every orifice.
Being slightly older and wiser, I have now learned to apply the patterns correctly. Now using patterns simply is a guide, I've been able to cut my OO design time significantly. Rather than sometimes going into a very deep think to solve a design problem, or worse yet, designing myself into a corner, I can usually, and rather quickly, come up with the pattern that will properly apply to the system I'm designing. Its also helped with coming up with designs that strongly encourage code reuse.
I highly recommend Design Patterns
, but the reader must
must have a lot of common sense or a good amount of experience to get the full affect of this book. Reading it because "Patterns are kewl!" will likely lead to poorly designed programs and heartache when you try to fix them.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||