DEV Community

Cover image for Is the design pattern so important on application
Murilo Lodovico
Murilo Lodovico

Posted on

3

Is the design pattern so important on application

In my opinion, a design pattern is like a set of methods and development approaches that not only help the developer responsible for creating the application but also make it easier for others who will implement new features, fix bugs, and carry out future updates.

No company, application, or service is strictly required to adopt methods such as design patterns. However, choosing not to implement these methodologies — among others — often makes the project harder to understand and develop, especially as it scales. Moreover, the absence of such patterns can negatively affect the maintainability and performance of the application, making the development process more prone to errors and rework. Once the use of design patterns becomes an integral part of the software development process, all the previously mentioned points turn into clear advantages, as long as the right patterns are applied to each context and situation. Otherwise, using design patterns becomes counterproductive, as each pattern was designed with a specific purpose, whether to enhance code readability, promote standardization, or abstract the architecture efficiently. Therefore, it's essential to understand the project’s needs before opting for any design pattern, ensuring that its application truly brings long-term benefits to the software lifecycle.

I make an effort to read and understand as much as possible about the topics I discuss in my articles, as I believe that a solid knowledge base is essential to create relevant and well-supported content. For this reason, I constantly seek sources of inspiration and learning, such as specialized books and trustworthy articles. Below, I share some of these resources that have been crucial for my education and for the development of the ideas I present. So some links that I use to learn more or books:

Sites

Books

  • Clean Architecture: A Craftsman's Guide to Software Structure and Design
  • Clean Code: A Handbook of Agile Software Craftsmanship
  • Patterns of Enterprise Application Architecture
  • Refactoring to Patterns

image to present myself

Image of Datadog

The Essential Toolkit for Front-end Developers

Take a user-centric approach to front-end monitoring that evolves alongside increasingly complex frameworks and single-page applications.

Get The Kit

Top comments (2)

Collapse
 
xwero profile image
david duymelinck • Edited

For me there are two sides to design patterns; architectural en engineering.

The architectural way to use design patterns is centred around communication.
When I say facade, people think this is a way to make the interface of certain functionality simpler.

The engineering way to use design patterns is implementing the pattern.
A facade can be a singleton or an abstract factory, depending on what fits best for the application.

I love the refactoring.guru site.

Collapse
 
mlodovico profile image
Murilo Lodovico

I agree with you, David. There are different points of view that can lead to different interpretations. For this reason, and depending on the context, it may be necessary to provide further clarification.

Eliminate Context Switching and Maximize Productivity

Pieces.app

Pieces Copilot is your personalized workflow assistant, working alongside your favorite apps. Ask questions about entire repositories, generate contextualized code, save and reuse useful snippets, and streamline your development process.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay