The best video on visitor pattern. Especially showing code snippets in the same structure that mimic its uml diagrams made this pattern understandable. Great technique. It worked wonders for this video.
wow kya samjate ho aap itna complex subject design pattern me samaj nahi pa raha tha ki exam me kya likhu kese karunga lekin aapke video dekhne ke baad sab aasan lag raha hai. me jab search karta kuch to likhta hu "this design pattern by concept and coding". Thank you so much.
Another possible difference between Strategy and Visitor can be that Strategy uses composition to store different strategies where as Visitor is directly using double dispatch to call the required operation.
This is a great video! I have few questions though. In the example we have 3 rooms, what if we add new rooms? If we see the 2 problems it is trying to solve 1. If we add a 4th room, we need to add a implementation of visit in all of the visitors which in turn is modifying the existing class(Visitor in this case) 2. If we add more and more rooms, the class would get bigger and bigger So instead of adding more methods and making the class bigger, aren't we doing the same to visitor if we add more room?
I think you missed about the advantage of visitor pattern - the visitor would not be aware of structure of hosting classes. The host class would unravel it's children , let visitor traverse through it and collect information. I think that's part where algorithm is separated from operations / actions possible on it.
Thanks for this amazing explanation. I had a doubt, you told we add new operations without touching existing classes, but if we add new room like SuiteRoom, we will need to modify all visitors: RoomPricingVisitor, RoomMaintenanceVisitor to add new visit methods for SuiteRoom, so we will be change structure of existing classes here, right?
Lets say that in the future a new room type is added, then we need to add its corresponding visit() function in all the already tested implementing visitor classes, is there a way to handle this without touching the tested classes ?
Yes, as compare to “count-of-adding-new-room-type” with “count-of-adding-new-functions” is can be huge. so we can say that visitor pattern don’t completely removes re-testing and vertical growth of classes instead we can say it “minimizes” them.
Hi, Great videos. Ive read multiple resources. However, your explanation on all patterns is very clear. On the next videos: Can we take some code from some repo and think of where all there is scope for improvement and which Design Pattern can help us solving it. This helps in identifying the actual design pattern needed and very much needed in our real world.
Nice vedio. graet explanantion. can we declare Roomvisitor as below. interface RoomVisitor{ void visit(RoomElement element); } if new roomtype added in future.
When you approach a problem in interview or in your work. How do you think like this design pattern can work? I know in every pattern video you have told when it can be used but still it's not a piece of cake to figure out the design pattern Eg: In Apply Coupon Video of yours, I implemented without Decorator but you used Decorator. How come you or anyone think in that direction? If you can share insights, it might help others as well.
Lets say that in the future a new room type is added, then we need to add its corresponding visit() function in all the visitors so here we are again modifying the existing code to accommodate the new room, will this not violate open/closed principle?
When using the Visitor pattern, you define a separate visitor interface and implement different visitor classes to perform operations on elements of an object structure. In Java, this typically involves implementing the accept method in each element class, which takes a visitor as an argument. A violation of LSP could occur if adding new element subclasses requires modifying the visitor interface or any of its implementing classes. If this modification causes unexpected behavior or forces changes in existing visitor implementations, it could potentially break the principle.
I can understand the things but sometimes I feel like better to do simple code without this kind of design pattern. Simple code is always easy to understand and update.
Definitely they are, but if you see, Java lib which we are using are full of usage of design patterns. So these principles and pattern do have an impact on scalability.
sir in command pattern whats the role of invoker apart from applying undo feature like if we don't want undo feature then client already has reference to command and the receiver so client can directly call commands execute method and still there is no tight coupling between client and receiver and in uml why client doesn't have a HAS-A relation with invoker , plz reply sir
think about it like this: u can perform operations on a TV with a remote, but u can also do things like changing the channel and increasing/decreasing the volume directly by interacting with the TV also, then what is the use of remote ?
Shubham, you will find many patterns similar and doing same thing, only thing differs is intention. Strategy is Behavioral patterns which more focus on how to divide the responsibilities between objects (or in simple term how different objects should communicate whith each other) while bridge patterns is a structural pattern, which focus on how to organise objects to form a large structure. Ultimately both solution looks same but they tried to solve diff things, and same thing you find with many other patterns which look similar
Hi @ConceptandCoding ,, Thank you so much for such great content. Can you please make LLD videos on Swiggy / Zomato && Make my Trip, if possible. It will be very helpful.
this pattern is not making any sense. First we say to avoid retest of code we extract operation logic to new class. But what if in future We add a new room and we have multiple visitor, we would need to change all visitor classes
Great Video, but why did you change your language from Hindi to English. Your videos in Hindi were much more involving. It's very easy to understand stuff in our mother tongue.
The best video on visitor pattern. Especially showing code snippets in the same structure that mimic its uml diagrams made this pattern understandable. Great technique. It worked wonders for this video.
Best video I seen today which clear my doubt , Thank you buddy
wow kya samjate ho aap itna complex subject design pattern me samaj nahi pa raha tha ki exam me kya likhu kese karunga lekin aapke video dekhne ke baad sab aasan lag raha hai. me jab search karta kuch to likhta hu "this design pattern by concept and coding". Thank you so much.
Thanks
Another possible difference between Strategy and Visitor can be that Strategy uses composition to store different strategies where as Visitor is directly using double dispatch to call the required operation.
You are a talented teacher..
This is a great video! I have few questions though.
In the example we have 3 rooms, what if we add new rooms? If we see the 2 problems it is trying to solve
1. If we add a 4th room, we need to add a implementation of visit in all of the visitors which in turn is modifying the existing class(Visitor in this case)
2. If we add more and more rooms, the class would get bigger and bigger
So instead of adding more methods and making the class bigger, aren't we doing the same to visitor if we add more room?
Explained with good example. Additional info about strategy pattern comparison gives even more context to the explanation. Appreciated 👍
I think you missed about the advantage of visitor pattern - the visitor would not be aware of structure of hosting classes. The host class would unravel it's children , let visitor traverse through it and collect information. I think that's part where algorithm is separated from operations / actions possible on it.
Thanks for this amazing explanation. I had a doubt, you told we add new operations without touching existing classes, but if we add new room like SuiteRoom, we will need to modify all visitors: RoomPricingVisitor, RoomMaintenanceVisitor to add new visit methods for SuiteRoom, so we will be change structure of existing classes here, right?
Lets say that in the future a new room type is added, then we need to add its corresponding visit() function in all the already tested implementing visitor classes, is there a way to handle this without touching the tested classes ?
Actually this is one of the disadvantage of Visitor pattern.
Yes, as compare to “count-of-adding-new-room-type” with “count-of-adding-new-functions” is can be huge. so we can say that visitor pattern don’t completely removes re-testing and vertical growth of classes instead we can say it “minimizes” them.
Hi,
Great videos. Ive read multiple resources. However, your explanation on all patterns is very clear.
On the next videos: Can we take some code from some repo and think of where all there is scope for improvement and which Design Pattern can help us solving it. This helps in identifying the actual design pattern needed and very much needed in our real world.
Awesome input, thanks, will add it to my bucket list
Hi, what do you use to create these UML diagrams? @ConceptandCoding ?
Wacom pad and any draw application like OneNote
Great tutorial so far I have gone through
Thanks
Nice vedio. graet explanantion.
can we declare Roomvisitor as below.
interface RoomVisitor{
void visit(RoomElement element);
}
if new roomtype added in future.
When you approach a problem in interview or in your work. How do you think like this design pattern can work?
I know in every pattern video you have told when it can be used but still it's not a piece of cake to figure out the design pattern
Eg: In Apply Coupon Video of yours, I implemented without Decorator but you used Decorator. How come you or anyone think in that direction? If you can share insights, it might help others as well.
That's the game of problem solving ability companies look for. It comes with practice and many refer it as experience.😊😊😊
Lets say that in the future a new room type is added, then we need to add its corresponding visit() function in all the visitors so here we are again modifying the existing code to accommodate the new room, will this not violate open/closed principle?
When using the Visitor pattern, you define a separate visitor interface and implement different visitor classes to perform operations on elements of an object structure. In Java, this typically involves implementing the accept method in each element class, which takes a visitor as an argument.
A violation of LSP could occur if adding new element subclasses requires modifying the visitor interface or any of its implementing classes. If this modification causes unexpected behavior or forces changes in existing visitor implementations, it could potentially break the principle.
I can understand the things but sometimes I feel like better to do simple code without this kind of design pattern.
Simple code is always easy to understand and update.
Definitely they are, but if you see, Java lib which we are using are full of usage of design patterns.
So these principles and pattern do have an impact on scalability.
@ConceptandCoding can you please show where this design pattern used in java lib
sir in command pattern whats the role of invoker apart from applying undo feature like if we don't want undo feature then client already has reference to command and the receiver so client can directly call commands execute method and still there is no tight coupling between client and receiver and in uml why client doesn't have a HAS-A relation with invoker , plz reply sir
ack of the question
think about it like this: u can perform operations on a TV with a remote, but u can also do things like changing the channel and increasing/decreasing the volume directly by interacting with the TV also, then what is the use of remote ?
I am confuse that stratergy and bridge look similar because both focus on seprating a feature . Please help
Shubham, you will find many patterns similar and doing same thing,
only thing differs is intention.
Strategy is Behavioral patterns which more focus on how to divide the responsibilities between objects (or in simple term how different objects should communicate whith each other)
while bridge patterns is a structural pattern, which focus on how to organise objects to form a large structure.
Ultimately both solution looks same but they tried to solve diff things, and same thing you find with many other patterns which look similar
@@ConceptandCoding thank you for taking time and replying sir
can you share its pdf?
Hi @ConceptandCoding ,, Thank you so much for such great content. Can you please make LLD videos on Swiggy / Zomato && Make my Trip, if possible. It will be very helpful.
noted buddy and thanks for the feedback
@@ConceptandCoding Thank you :)
this pattern is not making any sense. First we say to avoid retest of code we extract operation logic to new class. But what if in future We add a new room and we have multiple visitor, we would need to change all visitor classes
Great Video, but why did you change your language from Hindi to English. Your videos in Hindi were much more involving. It's very easy to understand stuff in our mother tongue.