Thread by @Souvir

[THREAD]
As requested I'm starting a series of thread on design pattern.

First:
- An algorithm is a step-by-step recipe for performing some task
- A design pattern is like a blueprint: a structured collection of objects, associations, and actions to accomplish some goal

Definition:
A design pattern is a general repeatable solution to a commonly occurring problem in software design.
It isn't a finished design that can be transformed directly into code but a description or template for how to solve a problem in many different situations.

A design pattern can't be directly translated to code. It is a "strategy" that can be useful for the design of an application. It’s a relatively vague description of how to solve a problem at an architectural level, with an emphasis on flexibility and maintainability.

In other words, a design pattern is a way of structuring your code in order to elegantly express a relationship between functional components. You might use design patterns within the implementation of an algorithm.

"Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice" - Christopher Alexander

Conclusion, Design patterns:
- is Abstract and Flexible
- controls Structure
- a solution to a common but generic problem.
- a general solution to a general problem.
- often have to be implemented each time it is used.

Design patterns can be categorized in multiple ways.

The most popular is the following:
- Creational
- Structural
- Behavioral
- Concurrency
- Architectural

I'll review each category and most common patterns in future threads!