What is the Factory Pattern? | Software Design Principles

[@ThuyNguyen-bu9ge]

The factory pattern helps us to NOT repeat logic all over the place - there is one and only one place to create a new object. So if that new object some day needs new parameters or less parameters, then we don't need to change our code all over the place. We need to only update the Factory where the new object is created.

[@IUfidi]

nice.

[@dovias5665]

Why doesn't this have more views? That's premium content.

[@BeABetterDev]

Thank you so much for your kind words Dovias!

[@2810quocviet]

What a great video. After watching the video several times I've finally grasped the core concept.

[@aaa4363]

Thanks!

[@BeABetterDev]

Thank you so much!!!

[@hafsahmr9010]

The coding part really helps! Thank you so much! Would appreciate a video on Abstract Factory.

[@BeABetterDev]

Coming soon!

[@kais.alkotamy9798]

quite an amazing course, I just want to say something that I wish it could be added which is how to approach using one of them "the use cases"

[@frederickjavalera558]

Great content! Did you ever get around to creating the second video on the abstract factory pattern that you mentioned at the end of this video?

[@ThuyNguyen-bu9ge]

Very crisp, clear voice. Good teaching! Would you make a video about why we need the factory pattern - what problems the factory pattern is addressing?

[@BeABetterDev]

Hi Thuy, I see from your recent comment you figured out the value of this pattern! You hit the nail on the head :)

[@ganesh221b]

Thanks a lot Daniel, your videos are great!

[@BeABetterDev]

Thanks Ganesh! Glad you enjoy them :)

[@rezazaman1714]

Excellent, it made my understanding clear on Factory Method. Waiting for your next video on Abstract Factory Pattern.

[@jedgraves8399]

Super helpful. Thank you!

[@AmrMekkawy]

Great clear explanation

[@nitinakash3275]

Great contact.. Waiting for the second part

[@kshitizkumar2793]

If the branching logic is still there in the second approach, doesn't it still violate the open close principle ?

[@Preotasherpa]

Thank you so much.

[@BeABetterDev]

You're welcome Tahsin!

[@frotes]

Nice video. Would be interested in seeing the composition version you mentioned. I feel composition is the way to go for most things in OOP

[@avanthasiriwardana]

Good stuffs brother. Liked and Subscribed :)

[@BeABetterDev]

Thank you and welcome to the channel!

[@smirkedShoe]

Great clarification 👏. Do we have a SOLID principles playlist ? I couldn't find it

[@BeABetterDev]

Hi Naman! Not yet but this is a great suggestion!

[@lorenzoferri7876]

In the last part, when you describe the NYPizzaStore, you break the Open / Close principle anyway, right? wouldn't it be better and optimal to split It in two other classes (NYPepperoniPizzaStore and NYCheesePizzaStore)? I hope you clarify my question. Congratulations on the great video!

[@alsonyang230]

Second this question. Wouldn't the NYPizzaStore still violates O/C principle if there is a NYStyleHamPizza added? Does having the factory abstract class do any better than the simple factory class?

[@ayingtorres5938]

This is an awesome channel!

[@BeABetterDev]

Thanks Aying! Really appreciate the kind words.

[@ranjithaan5825]

did I miss the second part of Factory design pattern you have mentioned anywhere? could you please paste the link if you have posted on second part? thanks

[@GEhehloopf]

Could you go over the Visitor Design Pattern?

[@intuitorx]

Very helpful

[@BeABetterDev]

Thanks!

[@saedyousef]

This channel is so underrated ...

[@BeABetterDev]

Thanks Saed, I'm glad you think so :)

[@PoojaSharma-vt9xs]

Really very clear explanation.

[@BeABetterDev]

Thanks Pooja!

[@MrUnknowntraveller]

What blackboard tool are you using? Nice clear explanation. Thank you.

[@IUfidi]

Good. Liked. Subscribed.

[@BeABetterDev]

Thank you and welcome to the channel!

[@parthshah438]

could you please provide link for abstract factory deisgn pattern video as you have mentioned in video?

[@nehapandit1987]

Is the Second part of this is ready?

[@johnyonardpauly5601]

Dude, this looks like a paid udemy course. Thank you for this!

[@uzayrsyed6293]

Shouldn't all these methods be outside of the Pizza class pizza.prepare(), pizza.bake(), pizza.cut(), pizza.box(), createPizza() and instead maybe be in the Factory?

[@misoren9645]

I still didn't get it. Isn't the main problem described as "violating the Open/Close Principle"? If we were to add a new kind of Pizza Type, we still would need to modify the if/else type block anyways, so how did creating all that new logic helped to solve the problem if it's still there anyways. Great content though.

[@ihabhadjerci5238]

Great content thank you so much, I definitely subscribed, I have a question, what if we have added the ItalianStore Class and we give the user the right the store in the main class how would you know which Store will be choose and how would you handle it since we don't wanna to expose instantiation to client

[@mirzaaqeel]

Good material, can not see git hub link for the code you used in the example.

[@BeABetterDev]

Hi Muhammad, check out this link for the code repository: github.com/beabetterdevv/DesignPatterns/tree/master/patterns I still have plans to create the remainder videos, stay tuned in the next few months.

[@zemusic2736]

like your content, friend

[@BeABetterDev]

Thank you very much!

[@LoLLuL-d5m]

but now runner needs to know the concrete implementation of the factory, which is again an anti pattern, should we create factory for getting these factory?

[@alex-dk2rj]

I'm confused because there is thousands of variations of toppings on new york pizza, so is this method practical for this example? Wouldn't you have thousands of classes?

[@jakubrysiak3612]

Why do you need the order method, since all it seems to do is call the create method?

[@sagartyagi2450]

Isn't it simple Inheritance?? Why are we calling it a pattern?

[@GustavoRubio]

Midterm in 25 minutes boys. Time to set these videos to X2 speed

[@BeABetterDev]

Hope you did well!