Thanks for explaining it in such an easy manner. Another important benefit of the builder pattern which you brushed upon briefly is "immutability" which is something I have personally found out to be very useful in many cases.
I had so much difficulty in understanding the builder design pattern but you made it so simple to understand its concept. Love your videos. Keep posting as they are really helpful.
your way of explanation is really superb brother really ...... so good please make vedeos on data structures and algorithms as well. Once again thank you so much.😊
I believe it is not a problem. You are correct to avoid static methods but that is not what we have here, right? In the lines: Vehicle car = new Vehicle.VehicleBuilder("1500cc", 4).setAirbags(4).build(); and Vehicle bike = new Vehicle.VehicleBuilder("500cc",2).build(); The constructor of Vehicle.VehicleBuilder() gives us back our own instance of an object. The .setAirbags() and .build() calls are NOT static methods, they are instance methods of class Vehicle.VehicleBuilder. Good question to ask, because it would be a common mistake to make, but was not made here unless I am confused. Static modifier on the nested class means only that you do not need any instance of the outer class to call the constructor of the nested class, which is essential here, because we can't get an instance of the outer class until after we have an instance of the inner one. A bit tricky, but very cool.
I understand whole code. But i dont get why we do in seperate class? we can do same inside Vehicle class. If you will say me for private then my answer if we can set anything from vehiclebuilder then what kind of privacy is it.
Zero is the default value. For 'car' we called the function setAirbags, but for 'bike', we didn't call, so it initialized with default value, which is 0 because it's integer. So this what is required that if we're not setting other value, it'll set to default values.
If it wasn't static, we would already need an instance of the outer class to use it, so we would have a chicken-and-egg problem, right? Why nested at all instead of stand-alone separate class? We could do that and it would work, but when one class is very much associated with another, we will consider a static nested or inner class. Also, both static nested and (instance) inner classes can access all members, public, protected and private of the containing class. If it was a standalone class in the same package, in order to let that class access the members the members would need to be marked as default access, rather than private, so that is another reason we might choose this.
I watched another video and see a further very good reason why we do it this way. They avoided the nested static class you don't like by providing Setters for all the optionals, which to me almost makes the Builder class pointless. Here's the problem tho. You might set five or six things with the Builder, then when you are done with those and ready to actually build it, it can verify that your combination that you requested even makes any sense. Now, doing the sets one at a time you can't check that the combination is good. Let's say (not perfect example but shows what I mean) you want to say you are married, your anniversary is on April 1st and your wife's name is Taylor Swift. Doing a set on any one of these leaves us in a totally invalid state. You just set a date for your anniversary, but your object says you are not married. Maybe you are about to set the flag to say you are, or maybe you will forget to or setting the Anniversary was just a mistake. There's nothing my program can do at that point to prevent you from putting in nonsense combinations of data into the object. Sure, you aren't crazy about the static nested class (for some reason) but look at all the pain and suffering it can prevent us!
I have seen multiple videos, no one's clearer in explanation than you :). You're doing such an amazing work! Thank you so much!
Thanks for your nice feedback. Keep Watching.
Thanks for explaining it in such an easy manner. Another important benefit of the builder pattern which you brushed upon briefly is "immutability" which is something I have personally found out to be very useful in many cases.
Three minutes in and I already have to give a thumbs-up. Very clear, calm, and concise.
Thanks for your nice feedback. Keep Watching.
thank you .this helped me a lot.Some articles and videos are making it complex by taking complex examples.This is perfect and to the point.10/10
Thanks for your nice feedback. Keep Watching.
The best explanation I've seen. My instructor could learn a lot from you. Thank you. I've subbed.
Thanks for your nice feedback. Keep Watching. Sure share channel with him ;)
This is the greatest explanation of the builder method that I've ever seen. Thank you for the explanation!
I had so much difficulty in understanding the builder design pattern but you made it so simple to understand its concept. Love your videos. Keep posting as they are really helpful.
Thanks for your nice feedback. Keep Watching.
This was very simple and easy to understand. Thanks a lot.
5:50 if you want to skip the theory, though.
Thanks for your nice feedback. Keep Watching.
your way of explanation is really superb brother really ...... so good please make vedeos on data structures and algorithms as well. Once again thank you so much.😊
Very nice explanation, Thank you so much!!
Helps a lot to understand the concept thank you Coding Simplified team #KnowledgeSharingCodingSimplified
Thanks for your nice feedback. Keep Watching.
Very nice explanation with very easy example which helps is preparing for interviews. Thanks for uploading this.
Thanks for your feedback.
You're really such a good trainer ❤️
Thank you very much!! Best builder pattern video!
Thanks for your nice feedback. Keep Watching.
You have explained in a very simplified way and this makes it more easy to digest.👍 Thanks
Thanks Mukund for nice feedback. Keep Watching.
Thanks for explaining the concept .
Thanks for your nice feedback. Keep Watching.
Great explanation. Thank you so much
Very nice explanation but i have a doubt like can we update the value of parameter for second time....
explanation is too good, easily understand ..thanks
Thanks for your nice feedback. Keep Watching.
simple example and clear explanation.
Thanks for your nice feedback. Keep Watching.
Nice explanation Sir ❤
content is very easy to understand. Thanks
Thanks for your nice feedback. Keep Watching.
For the factory pattern I believe if you create a VehicleEnum and then put each to the VehicleFactory would be more descent
Great explanation, keep the good working going..
Thanks for your feedback. Keep Watching.
Thank you for sharing.good tutorial
Thanks for your nice feedback. Keep Watching.
Hi
Can you please guide me
For debugging what all buttons you are using
It's all basic buttons in Eclipse. On top, you can see all debugging buttons.
Don't you think Vehicle Builder violates Dependency Inversion Principle?
simple and great : Thanks a lot.
Thanks for your nice feedback. Keep Watching.
Your amazing, it's a great explanation.
Thanks for your nice feedback. Keep Watching.
Here Defining a builder method as static. It's not thread safe right? when multiple threads trying to create vehicle instace using this apporach.
I believe it is not a problem. You are correct to avoid static methods but that is not what we have here, right? In the lines:
Vehicle car = new Vehicle.VehicleBuilder("1500cc", 4).setAirbags(4).build();
and
Vehicle bike = new Vehicle.VehicleBuilder("500cc",2).build();
The constructor of Vehicle.VehicleBuilder() gives us back our own instance of an object.
The .setAirbags() and .build() calls are NOT static methods, they are instance methods of class Vehicle.VehicleBuilder. Good question to ask, because it would be a common mistake to make, but was not made here unless I am confused. Static modifier on the nested class means only that you do not need any instance of the outer class to call the constructor of the nested class, which is essential here, because we can't get an instance of the outer class until after we have an instance of the inner one.
A bit tricky, but very cool.
Hey, so based on 2:14 , the way we mark parameters as required=true/false in jcommander, does this come in BuilderPattern too? If yes, how?
I understand whole code. But i dont get why we do in seperate class? we can do same inside Vehicle class. If you will say me for private then my answer if we can set anything from vehiclebuilder then what kind of privacy is it.
Where did you set airBags default value to zero ?
Zero is the default value. For 'car' we called the function setAirbags, but for 'bike', we didn't call, so it initialized with default value, which is 0 because it's integer. So this what is required that if we're not setting other value, it'll set to default values.
thanks
Mind blowing sir
Thanks Sumit. Glad you liked it. Keep Watching.
What if I want to change airBags after vehicle is created ?
What is the reason for nested class as static ( builder)
If it wasn't static, we would already need an instance of the outer class to use it, so we would have a chicken-and-egg problem, right? Why nested at all instead of stand-alone separate class? We could do that and it would work, but when one class is very much associated with another, we will consider a static nested or inner class. Also, both static nested and (instance) inner classes can access all members, public, protected and private of the containing class. If it was a standalone class in the same package, in order to let that class access the members the members would need to be marked as default access, rather than private, so that is another reason we might choose this.
I watched another video and see a further very good reason why we do it this way. They avoided the nested static class you don't like by providing Setters for all the optionals, which to me almost makes the Builder class pointless. Here's the problem tho. You might set five or six things with the Builder, then when you are done with those and ready to actually build it, it can verify that your combination that you requested even makes any sense. Now, doing the sets one at a time you can't check that the combination is good. Let's say (not perfect example but shows what I mean) you want to say you are married, your anniversary is on April 1st and your wife's name is Taylor Swift. Doing a set on any one of these leaves us in a totally invalid state. You just set a date for your anniversary, but your object says you are not married. Maybe you are about to set the flag to say you are, or maybe you will forget to or setting the Anniversary was just a mistake.
There's nothing my program can do at that point to prevent you from putting in nonsense combinations of data into the object.
Sure, you aren't crazy about the static nested class (for some reason) but look at all the pain and suffering it can prevent us!
U r awesome bro
sir pls share the source code link .The link which you have shared is not working
Could you please check again. It seems to be working fine.
Чтож все индусы так коряво по английски говорят!?!
Bro you could have write in English ;)
Bekar pattern h
Helpful
Thanks for your nice feedback. Keep Watching :)
Great explanation...thanks a lot for making this video......!!!
Thanks for your nice feedback. Keep Watching.