for those who got error at 2:00, each of the setter method should return this, so that you can call method chaining in main

Delivered with such quality and clarity. Gold.

Glad I found this series. Such a clear, crisp and step by step process of explaining different concepts. Thank you ❤.

superb explanation ... thanks for making the video

Thanks a lot 🙏 If you want to use chain function calls, you should return "this" to return the object itself. ( It's forgotten in code. )

One of the best videos I've seen regarding this topic so far! Great work!

Great! Thanks for sharing. Really clear, keep up with these videos

Top video on builder pattern

This series is so clear and concise. There's great explanation, clear code and a relevant UML diagram which matches the code.

Best explanation I’ve come across

I loved the explanations 🥰

Great. I don't like real world examples like Cars but I still understood the concept very well even with audio only.

great video!

Awesome explaination

very good

At 2:00 the signature of the methods inside CarBuilder does not match the code. For example method id does not return a CarBuilder

Theses patterns seem overly complicated for no reason

These series are great, I have watched many videos and studied books about design patterns but these videos are engaging me. Excelente work!!!

crystal clear video thank you

Thx for this Pattern ! 😀

Thanks :)

Thanks, I'm Japanese. I can't understand English almost. But this video is perfect. I could understand builder pattern on this video than reading a textbook about gof in Japan. I admire you. thank you

You are so awesome !!

thank you very much for the video, the build method should be put within the Builder interface, I thanks for the answer and again thank you very much for the video

I loved you explanations, but in the builder class is missing "return this" without thit you cannot link the methods with '.'

I like the Builder Pattern in some usecases, but the usecase would need to be justified imo. I would rarely use it in place of a constructor, if ever. Let's say that the constructor has 10 properties and we want to create 1 million cars. Instead of performing ~11 operations (calling constructor, setting the 10 properties), we need to perform ~3 operations per property (calling the build method, setting the property and return the Builder). It won't matter in most scenarios, but in this hyperbolic example the CPU would do approximately 11 million operations in the constructor example and 33 million in the builder example. Having long constructors is also rarely an issue since we just use variables as arguments: new Car(id, brand, make, doors, engine, ...). Then we can just make the optional properties nullable. I'm only critiquing it's usecase for being a replacement for constructors. It can be very useful in certain usecases like the StringBuilder, DateTimeFormatter etc. It's also useful when you want to chain modify default/set properties, like the Locale: Locale locale = builder.setLanguage("en").setRegion("US").build(); I love using the Builder Pattern in this scenario. We can change all the properties that we want in one line, and we can ignore the Locale properties that we want to leave as default.

I have a question, I read in the internet that you can use a public static inner class as a Builder in the object you want to create to implement the Builder Pattern. Is this basically the same? What are the advantages / disadvantages doing it either way?

If the builder is not a part of class representation then how can it call it's constructor. And if there is no getter method for the class, how the client will be able to access it's field.

Do you think the Builder Pattern could be an effective way to build different kinds of AiControllers with different behaviours/states and abilities, say for an Orc, Goblin, Troll, etc? Would the architecture flow look like? Thanks

CarBuilder instead of duplicating Car fields, can contain Car and set it's fields via setters (restricted)?

2:48 if the Car constructor is private how does the CarBuilder build method construct the car class?

How can you implement a builder in a children class? I only want to set some parameters of the parent class, and the id in the children class.

At 2:24 so basically we are just hiding the ugly part. We also need the constructor with those nulls.

What is the meaning of making carSchema is this for to make different types of car like one implementation will make one kind of car and other is for different type. But this we can do inside director only. Than what is the meaning of carSchema. Plz explain