Have you ever been on a team where you need to start a project from scratch? That’s usually the case in many start-ups and other small companies.

There are so many different programming languages, architectures, and other concerns that it can be difficult to figure out where to start. That’s where design patterns come in.

A design pattern is like a template for your project. It uses certain conventions and you can expect a specific kind of behavior from it. These patterns were made up of many developers’ experiences so they are really like different sets of best practices.

And you and your team get to decide which set of best practices is the most useful for your project. Based on the design pattern you choose, you all will start to have expectations for what the code should be doing and what vocabulary you all will be using.

Programming design patterns can be used across all programming languages and can be used to fit any project because they only give you a general outline of a solution.

There are 23 official patterns from the book Design Patterns - Elements of Reusable Object-Oriented Software, which is considered one of the most influential books on object-oriented theory and software development.

In this article, I’m going to cover four of those design patterns just to give you some insight to what a few of the patterns are and when you would use them.

#design-pattern #web-development