How important are Design Patterns really? [closed]

Answer 1

The single biggest benefit of design patterns in my opinion is that it gives developers a common vocabulary to talk about software solutions.

If I say, "We should implement this using the singleton pattern", we have a common point of reference to begin discussing whether or not that is a good idea without me having to actually implement the solution first so you know what I mean.

Add in readability and maintainability that comes with familiar solutions to common problems, instead of every developer trying to solve the problem in their own way over an over again.

Pretty important. Software can be made without them, but it's certainly a lot harder.

Answer 2

While it can be useful to talk about design patterns sometimes, I tend to agree with those who consider them harmful in many situations.

The main argument I would make is that often they actually stop people from coming up with proper solutions to a specific problem. Instead of thinking about how to solve that particular problem, people try applying one design pattern after the other.

They also tend to hide language deficiencies. A lot of them are trivial in a language expressive enough. A prime example would be the Strategy pattern which is basically reinventing functional programming in a complicated fashion. Often people would be better off understanding the real programming principles instead of just talking pattern languages.

Having said that: I'd rather talk about patterns with someone than not having a common language at all. In that way they are important if there is no better option. If I can explain myself in more formal ways (e.g. algebras), then I stop caring about pattern languages. Of course some would claim I just invent my own pattern languages that way ;-)

Answer 3

I would say very

The trick with design patterns is learning where and when to use them. Then can do all sorts of things for you like:

1. Make your code more readable
2. Make it easy to maintain
3. Make it more flexible
4. And the list goes on...

But sometimes they can do the exact opposite of some of there benefits again its knowing how and when...

Have you ever tried to pull out a sliver with a framing hammer? You may love you framing hammer but its going to cause all sorts of problems if you try to use it that way...

I think that as you refactor you code it sometimes evolves into a particular pattern or you may have been using a pattern all along without realizing it.

Answer 4

Software Patterns are important whether you know you are using them or not... by definition.

A design pattern is simply a generalized, reusable solution to a commonly occurring problem.

You can either hack around until you re-invent the solution of every problem you encounter or you can learn the "patterns" that that programmers have been utilizing for generations. If you formalize your knowledge of most common, named patterns, you will have a common vocabulary to discuss and apply the solutions.