When should Design Patterns be used?

1. When the application being built today will not change, the code accurately captures all requirements, and there are no planned enhancements or features. The application you are building will be the first and last release.

2. Your application’s code requirements are unique. No software engineer has ever built anything like it. The program does not deal with any of these routing issues like object creation and event notification.

3. There is plenty of time to prototype all of your new design ideas. Alternatively, you are so confident of your ideas that they do not require any proof-of-concept testing.

4. Everyone on your team has worked together for twenty or so years. If you ask Bill to try the “thing-a-ma-jig” trick, he knows exactly what to do. The team already processes a common design vocabulary, so you don’t need to learn someone else’s.


Well… I read this in a book called Professional C# Design Patterns Applied. Anyway I can’t agree with all by 100%. What do you think?