unknown

7 Design Patterns EVERY Developer Should Know

I post all the articles I read and find interesting myself.

Mobile Experts 👉🏻 https://codigee.com

Codigee

Today, you’ll learn about 7 different software design patterns. Many of which you already use, whether you realize it or not. Because simply put, they are solutions to common programming problems that appear over and over again, regardless of the language or platform you’re using. That’s what a design pattern is. A repeatable solution to a software engineering problem. Templates that can be applied to multiple situations.
And back in 1994, these four developers now known as the Gang of Four, wrote this book documenting, cataloging, and formalizing 23 commonly used design patterns. So I’d highly recommend reading that book, as it’s still heavily applicable today. But all of these patterns fall into 3 distinct categories.
Creational patterns, are all about object creation. So instead of creating objects directly, these patterns give you more flexibility in how objects come into existence. Think of it like a pizza shop - you don’t just throw ingredients together, you might have a menu of pre-defined pizzas (Factory pattern), or let customers build their own piece by piece (Builder pattern).
Structural patterns, deal with how objects relate to each other. Think of them as blueprints for building larger structures from individual pieces. It’s like LEGO - you can take complex sets and create simplified instructions for building them. A Death Star has thousands of pieces, but the instruction manual breaks it down into manageable steps.
Behavioral patterns, handle communication between objects - how they interact and distribute responsibility. Which includes the greatest pattern of all time, the strategy pattern. Think of it like switching between different navigation apps - Google Maps for driving, AllTrails for hiking, Transit for public transport. Same goal, different strategies. In code:
The idea of patterns that can exist within software is really amazing. Being able to understand patterns and abstract them out and reuse a strategy to write software is one of the best things you can do, because no matter what software you write there are patterns that can make things simpler and make other people get up to speed.
0:00 3 Types of Patterns 
1:34 Singleton Pattern 
3:35 Builder Pattern 
5:21 Factory Pattern 
7:47 Twingate Security 
8:58 Facade Pattern 
12:56 Adapter Pattern 
16:18 Strategy Pattern 
20:03 Observer Pattern 
22:49 Know When to Use Each One

it’s a great video for beginners and more experienced devs alike.
We all forget a lot of these patterns along the way.
I mostly use the strategy and singleton patterns, but didn’t realize that until i watched this.
I have a problem with terminology in programming. Too many terms and many that overlap or do similar things, just over complicates talking about programming.
I prefer to stick with “write me a class for this object and include all the methods for that object” and write the views that use that class and interact with those objects, and write javascript interactions for the UI and make xhr/ajax/fetch/api requests [whatever you wanna call 'em] to pull in additional data using the same classes/objects.
I see few cases for things to be more complicated than that.
And i will absolutely fail any questions about terminology any day, but i can still build just about anything on the internet :)

You just secured a spot in heaven! 😂

Thank you <a href="https://app.daily.dev/makskulicki" data-mention-id="VytfcqIe6kkqXCeiczBK5" data-mention-username="makskulicki" translate="no">@makskulicki</a>, very usefull especcialy for developers who start their journey !