Factory Method Pattern – Design Patterns (ep 4)

Video series on Design Patterns for Object Oriented Languages. This time we look at the Factory Method Pattern.

💙 BUY MY BOOK:

► The playlist

► Head First: Design Patterns

► Design Patterns: Elements of Reusable Object-Oriented Software

💪 Patreon Community

📚 Products I Recommend

[thekonax]

This guy is already speaking in 1.5 speed. You are the best Christopher! Thank you

[kareemjeiroudi]

BTW, whenever I need a reference for design pattern, I would actually go back and watch your videos instead of Design Patterns by the gang of four, because you're incredibly good at explaining Object-Orientation concepts.
Please keep up your awesome work!

[Mitch_Crane]

Thank you Christopher for another helpful explanation on patterns. I cannot imagine how long it takes to edit all these jump cuts. God bless.

[BleachWizz]

I think I'm understanding why you're such a good teacher.
I can't identify how you're doing it, but you manage to move on and explain new things saying the same thing over and over and over again. But everytime you say it there's something new yo realise about it, the way you wrote the script of your videos (or just made them) is amazing.

[Nex_Addo]

I really appreciate you going through the logic of "Well why wouldn't we just do xyz", "we don't do that because then...". It really helped make it click that it's not just about being able to instantiate different sub-types, it's also about being able to instantiate them in specific, repeatable ways.

[ringo.gg.]

Dude you are fuckin amazing, I haven't found any other channel that explains and make clear the concept like you did.
Hope you make all the g.a.m.m.a patterns on this series, cheers !

[FionaCat]

The example in the book confused me to no end, but you described this so clearly. I think the missing piece for me was understanding the power of encapsulating different strategies for object creation. Once I understood that, it all clicked. Thanks so much, I hope you will continue with more tutorials!

[nikeshdevaki]

Nothing went to my mind when I watched this video for the first time. Then I went back and read this concept on "The Head First Design Patterns" book and then came back here. This time things are very relatable and visualizable. Now I following this method for all the patterns and its very helpful. I suggest the same for beginners.

[Sam-pqpk]

I come from other videos where everybody is giving great comments however the video is trash. I finally came to the right place where the explanation is actually good. Thank you Chris you should build a Java course someday!

[mbesurich]

This is the best explanation of this pattern! What could be better? Personaly for me - to show an example of what different way of creating products can contain different factories. This could help me to understand more clearly the benefit of using factories versus creating straight the products. But anyway, thank you very much for such understandable information delivery!

[phuctranbao]

Please know that you save my and so many others' lives. People, we need to protect this man at all costs!!!!

[SuperTurboCrash]

The editing in this video gave me heart palpitations.

[pionapior]

Like before a watch because you are a legend !

[asrajan]

Excellent, excellent, excellent lecture! Takes the time to introduce, repeat, cite examples, repeat.... No stupid power point slides... Talks to you and uses his hands and mouth to clearly explain...

[GeaForce]

Christopher: Check this book, it's really easy to understand
Also Christopher: Man, the examples on the book are catastrophic

[lima]

Just a positive comment: would be nice if you could implement these patterns into actual code after the lecture. Please release more videos!!!! Best..

[shanm]

I realized this is the best explanation after watching bunch of other videos on the same topic for couple of days. Thanks for making such a quality video on Factory Method Pattern.
At roots I propose to use this when
1. The client program is only interested in what kind of object is required, rather than what exact object is required. Best Example: I need level4 obstacle and not really bother to tell anything more than that.
2. When The client program is more concerned about how they co-relate when they get created more than one. Ex: random Animals are expected rather balanced animals from a Factory.
Awesome explanation. Thanks.

[shankar]

I completely agree with the fact that the book's example is causing more confusion than understanding. Your explanation at 5:35 is legendary and that's all I wanted to understand this pattern. Thanks a ton for that.

[SavageStyle]

Looks like you high but I was surprised how clearly you understand what people need to know, what they struggle with - all your examples are TOP. And how clearly you explaied everything! One of the best teachers I ever saw. Recommended!

[KellsCode]

This man is a true teacher. That's how it's done.