Understanding Builder Patterns from Scratch | Low Level Design | OOPS | Design Pattern | Java

[@vikram_saha7]

👏👏👏 What an explanation! Don't know why this video couldn't appear in my KZbin search results when I searched for a builder design pattern.

[@amitpandey9222]

I always think about learning design patterns but no one is explaining the real problem of when to use which design patterns. Recently, I found your channel on KZbin and learning things. Love the way you present the content and please keep adding the other design patterns & LLD things. Please create such good content. Keep doing it !!. Thanks a lot.

[@lavakumarkoyi7854]

Man, I like your explanation, because you create problem at every step and tries to solve the problem, with great explanation. I have watched many other people videos, they explain this design patterns as like some mugging subject, like we need to memorizie rather than thinking.

[@dreams1ist]

Excellent!! Understood builder design pattern clearly. 😊

[@trishulcurtis1810]

Excellent! Humble request to add more videos in this series

[@sahulraj9536]

Wowww this is really a great video, It really felt awesome watching this video because of your in-depth explanation and its very very clear. please try to continue the Design patterns/lld series it would really help a lot of people. i feel you might have stopped the series because it didn't get enough reach, but in long term i feel it will definitely get the reach please try to continue... thanks!!

[@sachindwivedi546]

Great Video! Problems solved and how it is solved in a simple way.

[@aman_deep21]

Awesome explanation, loved the way you covered the topic in smooth way and made it look like a cakewalk, thank you. Please cover all other design patterns in similar way.

[@arghya_0802]

Thank you so much sir for starting with this very important important topic. You really listen to the masses need!! Keep up the good work sir!!

[@rite2riddhi]

Thank you

[@pravenom5036]

holy shit! such a great video. Keep going on with this series man. I've also watched your graph playlist, it was great.Most of the design pattern stuff over the internet never really explains the "WHY" for the pattern. But you always make sure that you focus on the "WHY" a lot and its so great. I've seen the same in graph series when you explained dial's algo before going to djikstra.Thanks for this.

[@brilltwoant27]

amazing explanation riddhi da. I just started studying LLD and design patterns. feeling lucky to have started it from the right place!

[@asutoshmahapatro5903]

Thank you starting a fully unique playlist.please carry on.

[@rite2riddhi]

Thank you. Means a lot.

[@piyushpathak1186]

36 min dekh ke laga kon dekhe lekin kya mast video hai har ek cheez samajh aaya and now I am going to watch whole playlist Thank you for making this video

[@rite2riddhi]

Means a lot.

[@bhishambajaj8242]

Your explanation is simply awesome! I've been using this pattern with the @Builder annotation for quite a while, but your detailed explanation helped me truly understand its exact purpose and the need for it, what is going in the background.

[@sahilkachhap]

Please sir don't stop this series. Let it grow more n more. Very few people create videos on design patterns.

[@fuadhasan0362]

36 awesome minutes. Thank you very much.

[@VigneshSabapathi3]

I have never seen this much explanation . Thank you bro , want more videos Can you please create a video What are the skills we need to develop to become good developer?

[@yelururao1]

Thanks for Clear explanation ❤

[@ALLINONETV1]

Really loved this video ❤️ and it's very informative. Waiting for next video.....

[@rite2riddhi]

Dropping tomorrow 💯

[@pallavivarshney93]

very good video..cleared my concept on builder design pattern and many small things which I see in production code and wonder why done like this. Can you please share the code in description that would be really helful.

[@nancyagarwal8570]

Much needed, thanks for this series.✨🎊

[@eduflex7931]

nice video Sir. helpful for dsa freshers new to system design. Please continue the playlist in the same manner: intuition + explanation

[@suheabkhan2546]

Sarey design patterns cover kariyega riddhi bhai, just awesome explaination..Looking forward to learn them

[@rite2riddhi]

Thank you ❤️

[@pavansurve3723]

Thank You!

[@shivaarukonda2640]

sir, your explanation is too good. why don't you share the code?

[@Swaroop_Rath]

Waoo Riddhi Bhaiya...LLD shuru kar diya. Thanks for this. Aur bhaiya Graph ka series khatam hogya kya ya kuch aur questions agey add hongey ?

[@rite2riddhi]

add honge . topological sort baki hai

[@Swaroop_Rath]

@@rite2riddhi Ohkay bhaiya. Thanks for quick response.

[@R0hanThakur]

The video was so worth it I am seeing this and able to appreciate my work server code repo

[@shubhampokhriyal8491]

great.. will there be full lld playlist?

[@ravitiwari2160]

badhiyan padhaya bhai tumne... more power to you..

[@rite2riddhi]

Thank you

[@divyareddy7622]

thank you so much bhaiya!!!!

[@iamnoob7593]

Thanks riddhi

[@pooranivenkat3483]

Hi. Thanks for the great lecture. Pls upload the code😊

[@rohithchittibommala2002]

please continue this series !

[@rohithchittibommala2002]

I understand you are busy , but can we know when this series will continued

[@bhubanendramishra6785]

Insightful! But I am filled with doubts. The usage of 'this' keyword is baffling, more so because the code is working. How can a 'static' class 'DogBuilder' have an instance to refer to? 'this' keyword is used in every method in DogBuilder and as said in the video, it's returning an "instance" of the class "DogBuilder". How is this possible? The combination of static and 'this' keyword is confusing. Could you please reply to the question , forever grateful!

[@alikagarwala210]

Very helpful 👍 Love from UEMK

[@rite2riddhi]

❤️💯

[@codecspy3479]

Good video. I have a doubt. If a new client comes and asks for some extra methods/attributes which are not there in our Dog class, we do not try to modify the Dog class as this is violating SOLID principle(Open closed principle to be precise).The Open-Closed Principle requires that classes should be open for extension and closed to modification. So as done in the video is modifying the already defined Dog class a good thing to do ??

[@sadvikgowda6474]

Nice

[@rite2riddhi]

Thanks

[@akashingole2133]

Hi Riddhi, can we declare an enum to hold gender values? If yes, how will it be advantageous?

[@mickys4999]

I didnt understand one thing in builder pattern. What if we need to add another attribute to the static builder class like color of dog? Do we need to modify the static class? How will we implement it?

[@girunalaspurthinaveli3121]

We need to add new attribute both to dog & builder class and create setter & getter of new attribute in builder class

[@mickys4999]

@@girunalaspurthinaveli3121 Yeah but won't it violate the open closed principle

[@suheabkhan2546]

Can we expect all the design patterns in this series??

[@harshraj22_]

I had a few doubts: 1. For some developers, the object of dog class contains extra attributes which are not needed by them and is set to null. Is this an acceptable practice to have such classes with extra attributes ? 2. Is this pattern anyway helpful for languages which support default keyword arguments in constructors (eg. Python) ? 3. Shouldn't a Multiple Inheritance solve the problem better, as the client should inherit only the classes which contain the method that are needed, and so new class would have only those attributes which are needed by client (nothing extra) ?

[@rite2riddhi]

1. I think it should be fine. One use case which I can currently think of is while writing unit test cases when you want to test a particular functionality and don't want your object to be populated by data , irrelevant to the test case. 2. you can use default parameters. I think it's there in java as well using ellipsis. But still you have to enforce the client to remember the order. And it is also not backward compatible as I mentioned. To top it all off , it doesnt help in code readability when , you pass so many parameters inside the constructor. 3. Multiple inheritance is not supported in java. Hope I was able to clarify your doubts

[@obsessiveDreamer]

​@@rite2riddhifor the second question:- there is a concept called named argument by which u can pass the argument in any order into a function, so basically if a constructor has a default parameter value then we can achieve all possible combinations of constructor by using name argument.

[@rite2riddhi]

@@obsessiveDreamer right.

[@nkalra0123]

why are you not using intellij IDEA?

[@KrishnaSingh-yc7wp]

Q. How this Builder pattern code implementing immutability of gender attribute ? A. Now you can define set method inside Dog class directly for the attribute you wish to update in future. But for email attribute which we want to keep immutable don't define setEmail method inside Dog class for email attributes. So once Builder object is constructed now its in Dog class hands to provide client with the set method for selected attribute I hope this understanding is correct

[@varshneyshuchi]

Please cover all the design pattern

[@nightgamer8953]

Hi , I have one question. 1) What if we want to change the Dog Name again after the Dog is created? we should expose Dog's setName method to client - ( is this correct ) anyone please clarify it.

[@pratikdey8062]

At times I thaugh I was watching striver's videos xd

[@hell-o8470]

code link pls?

[@pradeepravi9608]

Sir please make more videos in LLD and HLD

[@rite2riddhi]

From Jan

[@pradeepravi9608]

@@rite2riddhi thanks sir

[@atulsingh9266]

please complete the series

[@atulsingh9266]

Recently I watch your video posted on @technical sunega

[@harshitpandey7521]

DogBuilder is a static class. Then why are we using it as DogBuilder().setGender(“Male”). Shouldn’t it be DogBuilder.setGender(“Male”)?

[@rite2riddhi]

SetGender() is not static thats why😅

[@AshishGusain17]

Can you share the code too?

[@tuhinmukherjee8141]

Bruno might identify as a female. You never know.

[@test-tj3jk]

Just use lombok , it will save you a ton of time , you can thanks me later.................

[@rite2riddhi]

I know , it helps in getters and setters. But don't want to confuse people with it and keep things simple. Thanks for the suggestion though