Design Patterns: Factories

This is the sixth of an eight part series where Robert is joined by Phil Japikse to discuss design patterns. A design pattern is a best practice you can use in your code to solve a common problem. In this episode, Phil demonstrates the Simple Factory, Factory Method and Abstract Factory patterns. The Simple Factory pattern encapsulates object creation in one place. The Factory Method pattern uses factory methods to deal with the problem of creating objects without having to specify the exact class of the object that will be created. The Abstract Factory pattern provides a way to encapsulate a group of individual factories that have a common theme without specifying their concrete classes.
Resources:
- Sample code: github.com/skimedic/presentat...
- Design Patterns: Elements of Reusable Object-Oriented Software book: www.amazon.com/Design-Pattern...
- Head First Design Patterns book: www.amazon.com/Head-First-Des...

[@rakeshkulkarni2125]

I really like the type of questions the host asks, these are the type of the question I usually have, like "you eventually have to create an instance" type of questions, and then the teacher says, creating and using is separated, really great series. Thank you for this Microsoft.

Can you group all videos in Design Pattern series into to one play list ? many thanks :)

[@fwd79]

Full list for this series: 0. SOLID Design Patterns (start from here): kzbin.info/www/bejne/l5jOiIyGish_psk 1. Design Patterns: Command/Memento: kzbin.info/www/bejne/sIPFeZ96mtShaac 2. Design Patterns: Strategy: kzbin.info/www/bejne/h4usp5-krpaCpM0 3. Design Patterns: Template Method: kzbin.info/www/bejne/g5ekp6Zmo56og9U 4. Design Patterns: Observer and Publish-Subscribe: kzbin.info/www/bejne/bWPFlZR6oZl-gq8 5. Design Patterns: Singleton: kzbin.info/www/bejne/qZOwfWaue62FmKs 6. Design Patterns: Factories: kzbin.info/www/bejne/gHbOaHWVfLp4qMU 7. Design Patterns: Adapter and Façade: kzbin.info/www/bejne/jorEYaWjh7KNZ7M 8. Design Patterns: Decorator: kzbin.info/www/bejne/bIGzfoVmfLylkLM

[@ThePrinceSadie]

@@fwd79 MVP

[@evergreen-]

@@ThePrinceSadie here's that list in an actual playlist created by somebody: kzbin.info/aero/PLT2NrqLzZng3YMek58eVZVkBiW3NyVSef

[@joshfraser3991]

Great videos by Phil and Tom! I wish I ould see more by Phil!

[@fwd79]

Full list for this series: 0. SOLID Design Patterns (start from here): kzbin.info/www/bejne/l5jOiIyGish_psk 1. Design Patterns: Command/Memento: kzbin.info/www/bejne/sIPFeZ96mtShaac 2. Design Patterns: Strategy: kzbin.info/www/bejne/h4usp5-krpaCpM0 3. Design Patterns: Template Method: kzbin.info/www/bejne/g5ekp6Zmo56og9U 4. Design Patterns: Observer and Publish-Subscribe: kzbin.info/www/bejne/bWPFlZR6oZl-gq8 5. Design Patterns: Singleton: kzbin.info/www/bejne/qZOwfWaue62FmKs 6. Design Patterns: Factories: kzbin.info/www/bejne/gHbOaHWVfLp4qMU 7. Design Patterns: Adapter and Façade: kzbin.info/www/bejne/jorEYaWjh7KNZ7M 8. Design Patterns: Decorator: kzbin.info/www/bejne/bIGzfoVmfLylkLM

[@samihimas]

Hi, thank you for your comment. Do we need to follow those videos in a specific order? Thank you.

[@muxahx3096]

This is MOST CLEAREST exploration I have seen or read. My deep respect! This guy explains the problem and roots of the pattern. step buy step. p.s. really want to give this video +100500

[@hpandeymail]

Namastey Sir 🙏.. You are simply super . 2 of you on screen make it that much natural and easy environment for learning .. thanks for sharing the knowledge 🙂

[@srinarasimhakatte9241]

Phil, Is there any reason why you have used IPizza interface as well as Pizza abstract class where you have inherited the abstract class Pizza from IPizza?

[@sasukesarutobi3862]

"If you write something once, you should encapsulate it. If you write the same thing twice, you need to back up and encapsulate it. If you write the same thing three times I would ask you to stop being a programmer." 😂

[@rohitgalgali5512]

Hi, these episodes helped me alot. Thanks alot. Can you please take a session on "Code to interface" topic. That will be really helpful! Kind regards.

[@slavakotelnikov2440]

Is it possible to get code samples they use in the video?

[@peteredenburg6464]

I must be doing something wrong. In VS2017 prof I installed the 4.7 .NET Framework (NDP47-DevPack-KB3186612-ENU.exe). I created a new solution and added both the CreationalPatterns and the CreationalPatternsTests. At the 3:40 minute mark the code was shown for the first time and you had the SimpleFactoryTests.cs file on screen. When I open that file I get a warning about these lines: line 15 'using Xunit; | line 19 [Collection("CreationalPatternsTests")] | line 23 [Theory] | line 24 [InlineData(PizzaType.NewYork)] | line 41 Assert.NotNull(pizza as NewYorkPizza); | line 43 [Fact] and finally line 48 Assert.NotNull(sut as NewYorkPizza); Some of these line are also in the other Test.cs files on other line numbers. So this is about things I need get into this project dealing with testing. I have not yet learned about that, but I would like to follow along and participate. What must I do? Thanks in advance.

[@yummyexpress92]

9:29 It is probably an enterprise feature because I can't find it in pro

[@rezaz7167]

These guys make me anxious!! 😕

[@yeaitsme6834]

The car metaphor was like really confusing...

[@joshfraser3991]

I found it very helpful! To each there own

[@TonyTigerTonyTiger]

@@joshfraser3991 *their

[@xXL1VE4IDE4LSXx]

I mean the guy wanted to be addressed by the name of filter pixie... or something like that. What can you expect?

[@DiamondGB]

"Umbrella Corp" 0:23

[@TonyTigerTonyTiger]

Surprised more people haven't commented on that

[@kaidzz]

I think it's okay if you guys are looking at the camera, not sure though if you're comfortable with that.

[@Coffeecupdev]

Copy and paste and now "Clipboard inherit" heheh Good one.

[@chudchadanstud]

lol the pizza example is from the head first into design patterns book.

[@tothimre7950]

Not bad videos about Design Patterns, however this one is quite bad. By definition Abstract Factory is: "Provide an interface for creating families of related or dependent objects without specifying their concrete classes." The key here is "families of related or dependent objects"!! In the video there is an abstract class which has a factory which != Abstract Factory...

[@olegsuprun7590]

true, but this is still viable, the main point of abstract factory is that it is injected or passed into client as an interface

[@omirrrr]

Didn't know Gino D'Acampo was into coding

[@yapayzeka]

i hate these pizza examples they are everywhere and so confusing. the car example at the beginning is awesome.

[@xXL1VE4IDE4LSXx]

I feel so sad for Robert Greene Cx

[@TonyTigerTonyTiger]

I have an idea. Instead of sticking to 1 analogy, how about we use 4 or 5. We can start by talking about a car analogy, then move on to a pizza analogy, then move on to an Amazon Prime delivery analogy, then move on to an analogy about mayors making bets on the World Series, ...

[@codeintermediate4529]

Factory method is explained well in this video - kzbin.info/www/bejne/qpWwgJebmtyHpMU

[@debunkingcars2359]

Visual studio lesson, but the instructor has a Rider sticker 🤔

[@FirstContactX]

Thats the Resharper logo. Rider is the RD not R#

[@TonyTigerTonyTiger]

I have another idea. Instead of talking about just factories, let's also talk about singletons, inversion of control, template pattern, command pattern, etc.

[@TonyTigerTonyTiger]

So this guy is a fan of over-engineering. Even if you have just 1 class - not a set of 2 or more related classes - you should have an interface for it?? Because OCP? Abusing the OCP is not good design.

[@pmanha]

He not only adressses that but also explains why you might do it. In summary, if you can anticipate that you will need such a thing, you will end up saving time if you build it from the get go. And why is that abusing the OCP? Example: if you are developing the data repository for an application using sql server as the database, but some time down the line you need to have the option to use mysql, or any other, will the actions of said repository not stay the same for whatever engine you use on the backend and chuck the nitty gritty of the instantiation of that repository to the implementation? And I think they mention this in passing but: as a best practice, its up to you to judge the applicability of such best practice to your work.

[@FleetingDream755]

@@pmanha but isn't this a recipe for over-enginerring? It violates the KISS principle. If we don't need another data store, then we don't code it. Isn't that just doing more than you need to because of a "might"? This is in general, data sources are usually coded to interfaces but in general, if the requirement is to create A, I shouldn't anticipate B and code for it because it's wasting time. Unless something in the requirements suggests such a change might come. Otherwise it's gold-plating. Of course I could be wrong.

[@GenericName0]

No offense, but this was a terrible explanation.