Exploring Design Patterns: Is It Worth the Effort?

[Tsunami]

Hiya,


so, design patterns: worth taking a look into it, or a dead-end street?

I thought it sounded very interesting, but then I read this on Wikipedia:

Peter Norvig provides a similar argument - he demonstrates that 16 out of the 23 patterns in the Design Patterns book (which is primarily focused on C++) are simplified or eliminated (via direct language support) in Lisp or Dylan.[4]

Any thoughts from people with more expertise?

 

[nmtim]

If you're into OO, you should check it out. Design patterns address common situations that challenge OO principles. The standard book is by the "Gang of Four", called "Design Patterns". It has stuff that any OO designer should know, if for no other reason than vocabulary. It ain't going to end hunger, but it might keep you from reinventing the wheel.

CS people love to tell you how they used Lisp to solve all the world's problems thirty years ago, a hundred times better than you ever could, and they can prove it to boot. So how come the world has problems? And 30,000,001 unreadable emacs scripts?

 

[Nikimathew]

“Pattern” as the name suggests, means series of events occurring in a definite order. The patterns can be found in Java and J2ee technologies also. Many a times, we find that there is a particular way of tackling a problem. This way is easy and has been used many times successfully by a number of people earlier also. This method becomes a pattern.