Комментарии:
This is simple factory only. Not a factory pattern.
ОтветитьWhy have you stopped making videos. You don't how popular are your videos amongst students
ОтветитьHello mam, it looks like you're using premium features of IntelliJ , is it provided by your company or you bought the license on your own ?
ОтветитьDoubt:-
Is it the same method that's used to expose transaction API's of any bank to Amazon kind of 3rd party
Very well explained, have been searching for the videos and got this. You saved my life. Thank you ❤
Ответитьhere i think we need only one instance of CourseFactory, as it can be used to create a number of courses
ОтветитьHi Arpita, can you please take more use cases for Low-level design eg. Parking lot, School Management Systems, Hospital Management System, etc?
ОтветитьThis is an amazing video. Thank you for the wonderful explanation. First time I understood what Factory method pattern is actually meant for.
ОтветитьIf i create multiple concreate class based on vehicle type (TruckCreator, CarCreator, PlaneCreator) than based on type of vehicle if i return the creator class then that factory interface isnt working like facade class? please answer
ОтветитьThe best playlist on Design Patterns I have seen so far. Your way of explanation, examples, animations everything is top notch. Thanks a million to you.
ОтветитьBefore coming to this tutorial, I am having, doubts about design pattern but the way explained all the things it is easy to understand.
Thank you very much for such informative video ☺
Hi Yogita, can you please upload the code online and share the code url in the description. So that we can also try manipulating the code for the given design pattern.
ОтветитьNice explained
ОтветитьYou are amazing! Thanks for creating HLD, LLD, and Design patterns courses.
ОтветитьKINDLY SHARE THIS FACTORY METHOD PACKAGE THAT U HAVE IMPLEMENTED
ОтветитьHello and geetings from Bulgaria.
I like your energetic and well explained courses. However ...
I can see for last ... many years that it is the Indian scholars pushing the abstract methods while many other have given them up. For ex. the whole C# platform is based on the implementation of interfaces. Which in OOP terms gives us the "is a" relationships. Down the line that also help to implement the very modern now concepts like dependency injection and automatic unit tests. In both cases we can inject an object as another object's "has a", as well as we can inject a Mock object with pre-setup return values. That is for as long as those objects implement the desired interfaces.
I would love to engage you on small chat / discussion about that.
Thank you,
ILIIA
Great video, yogita.
btw, do you have someone for your video editing or how do you do it?
Where can I find the code?
ОтветитьExcellent explanation. Could you please add video for decorator design pattern?
ОтветитьUseful information, but maam dnt you think swich is violating OCP in case we have to add new type.. If not then can you please explain??
ОтветитьYou have not used createCourse method in factory method to create instance instead used new Class() directly.
ОтветитьI presented similar design in one of the tech interviews and was questioned on breaking OCP in factory class.
Though this is mostly taught by most authors for explaining the concept, in reality, we can avoid switch case with map so factory method just look up the map and return the value. Now to build the map, we have two choices
1. Provide register product method in factory so product can register itself and then can be returned
2. Use reflection to load classes in a map at startup. Map is maintained by factory class. Map key is identifier used in switch case and value is return type of factory method.
The Content is impressive, presentations. Which software used to create this content?
ОтветитьWhat is the program you use to create class diagrams???
ОтветитьSupreb expiation ❤️👌👌
You always made easy 😊
complete the playlist quickly
ОтветитьHello. I appreciate your effort. I have a question regarding the switch statement in your CourseFactory class as well as else-if statements in the vehicles example. Aren't those breaking the open-closed principle?
ОтветитьCrystal Clear Explanation. Thanks!
ОтветитьThank you for the video on an import pattern 👍
ОтветитьAs always on to the point and easy to understand . waiting for another design pattern video.
I have one off the topic query . how is your experience on LinkedIn Learning? dose it actually add some extra point when it comes to big companies ?I would really appreciate your response. Thanks !
Great example. If you can also explain the code flow through debugger, that will help to understand code much better.
ОтветитьBahut kam log samjha pate hai is tarah ! Aap unme se ek hai. Thanks for this explaination, I was wondering why this series is not resumed , Hoping you will continue and we will get best out of this series !
ОтветитьI am bca first year student . Can i become a software engineer? Plz tell me roadmap.
Ответитьthanks for such video
ОтветитьExcellent 👌👍
ОтветитьAfter long time
ОтветитьThe second example was little bit complicated but I really like createVehicle example. Thank you for explaining in easy manner.
Ответить