I hope you find this course useful. Learning more advanced OOP concepts can be daunting when you only know the fundamentals and want to learn the terminology, best practices and patterns to become a great object-oriented programmer. My goal for this course was to make is accessible to anyone, which is why I started out with the important OOP fundamentals -- such as encapsulation, composition, inheritance, UML, SOLID, etc. -- before introducing the 23 "Gang of Four" design patterns. Huge thanks to FreeCodeCamp for letting me publish to their channel and reach way more people than I could with my tiny channel: https://www.youtube.com/@doabledanny. Thanks :)
Perfect timing! I was struggling a bit with SOLID principles and OOP. Thanks.
I'm Gratitude for this amazing 11 hours video , keep goin on
Vote for complete DSA IN C#
Thank you very much for the detailed explanation. The approach of taking both laborious way, clean way clearly explains the value add. Watching this tutorial often is very helpful to understand SOLID principles application and design patterns and mindset.
This is THE best video I watched on FCC chanel till now
Needed this for work
Thank you! Thank you ! Thank you!!!!! My course on OOD c++ starts 25th Sept and this is the exact coursework required for me to work on !!!!!!!!!!! Thank you!!!!!!!
Great source, time to learn some (Factory, Builder, Singleton, Observer, Iterator, Strategy, Adapter, Facade)
The Abstraction example (Email Sevice 26:06 ) you illustrated looks similar to Encapsulation concept. I believe Abstraction can be implemented using abstract classes and interfaces, while Encapsulation can be implemented using access modifiers like private, protected, and public. Whats your thoughts?
1:21:21 so domain driven design is against Single Responsibility. Because there are business logic in entity
2:52:30 you violate the encapsulation here, also for every single state you have hvae to add a new State too, so there is no meaning in this example for the State pattern.
I had a question at 1:05:00 about Composition and Coupling earlier. In Composition class, it calls many other classes and causes more coupling, so why is it better than Inheritance?. A change in each part will cause the main class to break
Great topic for code writers 😊
And now after you have learned all of this and mind you this is all very useful, you can just replace everything with a function. You are welcome.
Builder pattern is useless if you can pass parameters with labels to constructor. I imagine that's why it is at tge end of video. In general it is a great master class video. I love it! ❤
Such a great topic. Thanks!
Thanks to the world, it's amazing.
2:54:17 What if you need to add more user roles? Wouldn’t this require you to update the publish method in each state and thus break SOLID?
@nurburgringkid