7 Design Patterns EVERY Developer Should Know

Comments · 861

• ZL

  @zlowolz2386 · 1 year ago

  Through my life, I mocked a lot of things, never once, have I mocked a singleton object.

  364

• IS

  @is-sam · 1 year ago

  I feel like all design patterns are just separation of concern. Even without ever knowing about them, if you just separate concerns logically you're gonna end up using them everywhere.

  368

• MA

  @mathiasbttger980 · 1 year ago

  most of these are really just: "you dont wanna do this manually every single time, make it a function"

  58

• KR

  @KronoXTapion · 10 months ago

  its like matthew mcconaughey is teaching me to code

  121

• MI

  @minerran · 7 months ago

  I am a 68 year old semi-retired developer who has been working with C++ for over 30 years and I can't think of a time when these concepts were explained better than in this video.  Well done sir!  Now we all know that if you put 10 developers in a meeting room, you'll get ten PASSIONATE opinions about EVERYTHING and all the birds are going to chirp in below about their favorite pattern being missing from the video (I'm tempted myself :) ) but this was an excellent summary.    You sold me Forrest, I'm subscribing immediately!

  15

• NU

  @null7178 · 3 months ago

  I have watched a lot of videos about design patterns, clean architecture, and DDD, and read some books, but I&apos;m not gonna lie: I only really learned them after 5 years of programming. Before that, I just did it because it looked pretty.<br><br>When you have a system that you need to refactor after 5 years, changing libs and adding some features, you know clearly what you did wrong in your architecture and what you did right.<br><br>so good look :)

  8

• VI

  @vinisciusrib · 9 days ago

  You had me a freedom units! Subscribed just for that…. First time hearing someone else saying that in the wild, keep up the amazing work!!! 😂🎉

  1

• ZE

  @Zeptonixmusic · 7 months ago

  Never in my life have I heard someone explain something in a way that is this clear, understandable, and engaging. I can&apos;t stop listening

  33

• KI

  @KineticCode · 1 year ago

  To newer developers - when you learn design patterns you generally think &quot;oh i can use this here!&quot; in every scenario, making design patterns your hammer and every code problem a nail. In my experience as a professional developer I have never - not once - deferred to the Design Patterns book to solve a problem. Everytime I had used one in my personal projects however - it was always an imperfect fit to a similar problem. You could say &quot;skill issue&quot; but I&apos;m just pointing out that you should not worry about these things before you&apos;re employed. Just make things!

  1.2K

• NO

  @NoFaceNoFace · 7 months ago

  I love how this video doesn’t just explain but also makes you feel smart at EXACTLY the perfect pace

  2

• NO

  @NOPE96 · 1 year ago

  To the new developers, stick to rules, rather than patterns. Stick to clean code structures, simple logic and descriptive readable code. SOLID, KISS and DRY principles basically.

  33

• WE

  @WestonJP88 · 1 year ago

  I REALLY like the analogies. That&apos;s the best way for me to grasp the actual concept. Just found you on YouTube, and I already like the content.

  67