Комментарии:
lol the pizza example is from the head first into design patterns book.
ОтветитьCopy and paste and now "Clipboard inherit" heheh Good one.
ОтветитьThese guys make me anxious!! 😕
Ответить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
I feel so sad for Robert Greene Cx
Ответить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 🙂
ОтветитьGreat videos by Phil and Tom! I wish I ould see more by Phil!
ОтветитьI think it's okay if you guys are looking at the camera, not sure though if you're comfortable with that.
Ответить"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." 😂
ОтветитьNo offense, but this was a terrible explanation.
ОтветитьDidn't know Gino D'Acampo was into coding
Ответить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.
ОтветитьI have another idea. Instead of talking about just factories, let's also talk about singletons, inversion of control, template pattern, command pattern, etc.
Ответить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, ...
ОтветитьVisual studio lesson, but the instructor has a Rider sticker 🤔
Ответитьi hate these pizza examples they are everywhere and so confusing. the car example at the beginning is awesome.
ОтветитьIs it possible to get code samples they use in the video?
Ответить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...
Ответить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?
ОтветитьCan you group all videos in Design Pattern series into to one play list ? many thanks :)
Ответить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.
ОтветитьThe car metaphor was like really confusing...
Ответить