Design Patterns : Not Reinventing the Wheel

Enhancing software development to the next level

Dario De Santis
Javarevisited

--

Photo by Florian Olivo on Unsplash

You are working on a project starting from scratch. Imagine you’ve received the minimal (functional or non-functional) requirements by your client and you have now (or maybe not) all the elements to evaluate how a business function can be supported by a technical solution. There are few questions you should have in mind in this phase :

How can we not reinvent the wheel?

How can we avoid later flaws in our code?

How can we improve our code quality?

Others might choose the easy way of start coding unordered stuffs and googling what you need to implement but not you. You will choose Design patterns.

What is a Design Pattern

In software engineering, a design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or a template for how to solve a problem that can be used in many different situations.

Mainly the concept of design patterns in software engineering was initiated thanks to the authors collectively known as Gang of Four (GOF), Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, whose in 1994 published a book titled Design…

--

--

Dario De Santis
Javarevisited

Software Architect, writing about Java, Spring, Microservices, Kubernetes and Cloud-native programming. Editor for Javarevisited.