Builder Pattern - design patterns (ep 11)

[@princeita7737]

jeez! its an A from me for an excellent explanation

[@Gellex1990]

Fantastic video. I'm subscribing, It helped solidify the design pattern for me, most of the other videos I see on design patterns tend to make them seem more complicated than which they really are. I will watch your other videos as well.

[@BBarters]

Glad it was helpful!

[@shreyashchoudhary2637]

While searching for any CS related subject on youtube I'm like hope some BBarters video come up! Great work!

[@bobslave7063]

Your real world examples rocks! Thank you.

[@allanpearson882]

18 minutes well spent. Buy this guy a bigger whiteboard !! :)

[@derrick7968]

Nice nice, I finally understand this pattern, thanks alot. And with a great real example... impressive.

[@vedantsharma5876]

Excellent Example with Excellent Explanation!

[@AnandVijay76]

excellent explanations about all the design patterns. really enjoyed watching all of them. since i play tennis, i liked the examples, and the subtle jokes about using the system for wimby and us open. (funny). keep it going. super work... really appreciate the videos!!

[@CookingWithMeenu4u]

kia baat hai bohat zabardast dost well done

[@letsCherishCoding]

Great explanation with a real world example. Nice

[@ravirajsaraganachari3038]

Thanks for nice explaintion with good real time scenario 🤗

[@BBarters]

Glad you liked it!

[@shiwang789]

I think its better to not have booking attribute in the notification class. we can send the booking object while calling the notify method.

[@vinayr5060]

excellent explanation. Thanks for taking up a real world scenario, Was tired of looking at car and pizza examples.

[@goelakshay0]

Is it similar to strategy design pattern ?

[@jagadishbalewadimath5036]

Great video. :) Easy to understand. Way of explaining using code is awesome. Felt very happy.

[@ShabnamKhan-cj4zc]

Awesome explanation in simplest manner.Thanks a lot.

[@GopiOraApps]

Excellent explanation..

[@abdulkamilf3648]

Best explanation !!

[@remoteXJunkie]

Hi, which design pattern shall we use to send notification mechanism while choosing between 3 different combinations(smsOnly,emailOnly,smsAndEmail). I guess factoryMethod would be a good choice if we have a common sending mechanism in all combinations.

[@shanmukhagadigi612]

may i please know why the strategy pattern does not work here

[@databiceps]

Very nice scenario and modelling explanation

[@anandpadamala451]

great explanation after watching your video i had subscribed.. why can't you explain with Java Code..

[@pramodhkampalli6908]

I'm awestruck by the way u explained this concept with such simplicity. Thanks a lot.

[@wattalavibes5039]

excellent explanation

[@chotijunkie]

Search many tutorial, finally find the solution, thanks 🙏

[@BBarters]

Glad you found it useful!

[@techtechtech8391]

Excellent... Waiting for bridge, adopter patterns.. Also pls tell me which pattern is suitable for logging different type of error.

[@rajchaudhary1645]

A good example. But let's suppose there one more notification is required, which requires a call for Gold Members(a new membership class), a Gold member has a personal Relationship manager, and now you have to update all the notification classes, and also a builder's function, add a new RelationShipManagerNotification. Instead of this can we use notification to notify like 1.Sms Notification 2.email notification. 3.Call Notification. Booking class will have a bool/bit which decides, who needs to notify. So when a new class Gold Member creates, we just add to add call notification bit. we don't need to modify any other class when a new call notification comes, just create CallNotification class, yes need to update builder class handle new bit What're your thoughts

[@PiterMorbid]

Thank you! GREAT EXAMPLE. Unfortunately this example does not use all of the builder pattern class hierarchy. For example, it lacks the director class and etc. But what the video does well is to illustrate when a builder is needed.

[@dustdreamer673]

The "Director" class is named as "Client Code" in the example since it's the class invoking the construction logic

[@weizhao900]

Agree that, here NotificationBuild is probably like director + builders. The notification is like "Product". So the construction is little different with normal builder pattern case i think.

[@saginithish2272]

Nice Explanation with good real-life example

[@sameerargade3892]

Great Example

[@julwania]

Like Approach I think example is complicated we can reduce multiple if else , avoid duplicate code, common add method can be useful.

[@mubarakkhan228]

Nicely explained with good examples

[@DG-wc8iz]

Cool way of teaching.. loved it

[@johnnguyen1655]

Again really cool example. Thanks alot!

[@sudhanshuverma9615]

Thanks, Good demonstration

[@damianwysokinski3285]

Many Thanks!

[@sayurirathnayake291]

nice explanation thank u

[@BBarters]

Glad you liked it!

[@abhishekmunigial6230]

Thank you.

[@BBarters]

You're welcome!

[@acd1234]

Who searched for clash of clans but end up here?

[@YadavAnoopKumar1987]

very nice explanation

[@crazeeealgorithms3236]

Hello Sir, Please Continue the Series.

[@chathuraariyathilaka]

this is same as observer design pattern

[@sarithabapuram]

True

[@aditchauhan876]

No

[@dineshkachhi35]

thanks you

[@dipaksinha007]

Thank you !!! :)

[@radiaben4344]

thanks

[@rupeshkokulla7066]

Shall i have ur number plzz brother u r really awesome super teaching I loved it the way u teach

[@Ty1er]

Can anybody explain what does the term "client code" mean ?

[@AdilKhan-vf2es]

any code calling a library or any other part of your own code

[@veerababubonthu927]

Your real world examples rocks! Thank you.