How do you know when to use design patterns? [closed]

by

Design patterns are supposed to provide a structure in which problems can be solved. When solving a real problem, you have to consider many tiny variations of a solution to that problem to see whether any fits a design pattern. In particular, you will probably need to generalise your problem, or its solution, in order to make a design pattern fit.

The answer is, it’s an art. Knowing the design patterns is certainly an important step. One way to get used to this sort of thing is to study applications of design patterns, not just the patterns. Seeing many different applications of one pattern can help you over time to get better at mapping a task onto a pattern.

More Related Contents:

  1. In a PHP project, what patterns exist to store, access and organize helper objects? [closed]
  2. How will I know when to create an interface?
  3. Naming Classes – How to avoid calling everything a “Manager”? [closed]
  4. Dependency Injection & Singleton Design pattern
  5. Is global constants an anti-pattern?
  6. Algorithms vs OOP [closed]
  7. Is there a use-case for singletons with database access in PHP?
  8. Why is Singleton considered an anti-pattern? [duplicate]
  9. How do the Proxy, Decorator, Adapter, and Bridge Patterns differ?
  10. Why do we need Abstract factory design pattern?
  11. What’s the difference between the Dependency Injection and Service Locator patterns?
  12. Which Typesafe Enum in C++ Are You Using?
  13. Where do I use delegates? [closed]
  14. Replacing if else statement with pattern
  15. Are utility classes evil? [closed]
  16. Using Command Design pattern
  17. Relational Database Design Patterns? [closed]
  18. Is UnitOfWork equals Transaction? Or it is more than that?
  19. When should I choose inheritance over an interface when designing C# class libraries? [closed]
  20. Factory, Abstract Factory and Factory Method
  21. If Singletons are bad then why is a Service Container good?
  22. Multiple Aggregates / Repositories in one Transaction
  23. Differences between Proxy and Decorator Pattern
  24. What’s the difference between design patterns and architectural patterns? [closed]
  25. adapter-Any real example of Adapter Pattern [closed]
  26. When should you use the singleton pattern instead of a static class? [closed]
  27. What is the difference between a fluent interface and the Builder pattern?
  28. When do we need decorator pattern?
  29. Difference betwen Visitor pattern & Double Dispatch
  30. Why doesn’t generic ICollection implement IReadOnlyCollection in .NET 4.5?

Leave a Comment