Hi there,
I’m Abanoub Samir, a Senior Frontend Engineer. and this is my series of articles to dive into some cool Frontend Design Patterns that can make your development work smoother and more efficient.
First, we should know what Design Patterns are.
What are Design Patterns?
Okay, after some searching, I found this answer on Design Patterns: Elements of Reusable Object-Oriented Software book
“Design patterns are solutions to general problems that software developers face during software design. A design pattern isn't a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations.“
Erich Gamma and his friends on this definition simply says that Design Patterns are solutions for problems that happened before to engineers like you and to help you to solve these problems quickly
They (not Erich Gamma and his friends but the community) made patterns to fasten your development process, The goal is to avoid reinventing the wheel by creating new solutions for problems that have already been discovered.
But the Important thing is to note that design patterns are not one-size-fits-all solutions.
If you faced a problem, you cannot simply say that pattern 1 must be used for problem 1.
The application of design patterns is not that straightforward. Instead, patterns serve as blueprints or descriptions for solving problems, but they do not provide exact solutions.
In practice, some problems may require combining elements from multiple patterns or using only certain ideas from a pattern rather than implementing the entire pattern.
This flexibility allows you to adapt the patterns to fit the specific needs of your project.
The End,
Wait me for Layout Patterns Article
Top comments (0)