Builder Pattern - Design Patterns 

The purpose of the Builder pattern is not just so that you can have optional parameters, it's to separate the construction of an object from its representation. Of course it's overkill if all your setters are going to be this.property = value, but it should be communicated that there's a massive benefit in using the pattern for cases where properties need to be validated before being set, or where setting them affects properties that had been set beforehand and so on.

Discovered your channel today, great series of videos, deserves more views!

Why don't we just put a setter and getter inside the User class?

Why not use "Object.assign(this, options)". It prevents use to write this.address = address etc

I'm surely not understanding something. Why even use a builder class in the first approach? afaik this is valid code (assuming that each set method returns _this_): const user = new User('Bob').setAge(22).setPhone(phone)

//why not just do this: class User{} var user=new User(); user.name="asd"; user.address=new Address("1","main");

Maybe I'm old school but I like the having semicolons. What does everyone else think?

Hi, why we've used build method in builder class ? Like what's wrong about using builder class.

Can we do this with keyword arguments like **kwargs in python

Can't you create the "functions" from the first builder in the user class itself? I don't see to point of the builder object.

Why don't we just put the setters method inside the user class with constructor having one parameter "name"

Great stuff buddy! Love these pattern explinations.

Imagine having builder class for every class taking care of super classes and child classes and composition

whats the idea behind creating new class called UserBuilder , we can simply add all set methods inside the class user itself ?

Shouldn't you use extends?

I am preparing for a technical test for applying to a company and during the interview they hinted out that the test is going to be mostly about design patters. I have never heard of design patterns before and every source on the internet is confusing. However, you are just making it simple and understandable by breaking down each pattern. Thank you so much for these videos. Subscribed.

There are very few good teachers and you are one of them. Amazingly explained. Loved it. And thanks for that.

Wouldn't it make more sense to create the User object inside the build method? That way you can build as many different User object as you want.

Thank you. Can you please tell how did you linked live server to javascript

Great stuff Kyle ! Loved these design patterns, keep up the good work :)

One thing that the Builder could be better than named Parameters is that : When the set.... method not only need set the value solely but has other logics which may relate to other parts. Please verify my guess. Thanks~

Why can't we simply use named parameters?

where did you get that boomerang in the background?

makes me really appreciate python kwargs

Beautiful article. Well explained, loved it. Thank you.

is there a video on Factory Design Pattern ?

I'm wondering if use the get and set method could be a way to solve this problem....thanks for the course, it help us a lot...ok I tested this way, but I realize we cannot declare a property class like private to try esolation them. So, the method getters and setters become useless in this case...I reviewed the case and we can has the private fields with # before the variable name

Bro you make coding simplified !!

Hi, I cannot find optional parameters on MDN or any other resourses. It looks like destructuring and thats all. No need to call it optional parameters? or I mistake?

Hey, can you say Backbone's way of initializing views and models, uses the second approach of the builder design pattern? Thanks !

for the second methode is that available just in javaScript ? and why not for other languages ?

Thanks for the clear and straightforward explanation of this concept! The examples you used helped me understand builders a lot better.

can we use this design pattern with react js?

Why don't you use const instead of let, when initiating class?

when I use the build method it returns an undefined even though I did exactly as you did !!!

I was so stuck trying to implement this functionality in my application but know I know this pattern it's made things incredibly easy, thanks for sharing.

Why can't a C++ Builder Pattern be this simple? haha

Your channel is underrated. (full stop!)

Thank you very much!!!

I tend to keep separate objects with data value from objects with methods and properties (getters and/or setters)… what wording (or naming) could be used to describe such objects in JavaScript? I would tend to use POJO but it’s not like it is something that is without any method or I would call it a JSON like object (obviously it wouldn’t have a constructor)…

builder pattern is confusing w/ all those "this' keywords.

Another great lesson. I'm a php guy, but this is all the same theory. I think accidently created builder class the other day, but now I know what it was I made.

Good explanation!

This is very useful. Perfect req fields

I like short videos that only explain one thing vs long tut videos that do it all.

Thanks for sharing !

Thank you so much, well explained and all

Please do a hair styling tutorial.

Thanks a lot for your effort.. BTW in builder class methods we are setting properties of actual user object , i.e. in setphone method setting phone property of user object so user is not immutable ... So why can't we set these properties individually from the client (calling code)?

Kyle, can you do a design pattern series? :)

Kyle, how about using optional parameters like constructor(name?, age?) ?

thanks, Kyle for the great video Kyle is it possible to remove the final build method and gets the same result if so then how

Can't you just remove 'age' and 'phone' from the constructor, and put the Setters in the User class?

This is good stuff. Glad someone did a good JS vid on this pattern. I think it would be nice to show more of the most powerful reason why you use the builder method which you did allude to at the very end. When an object ends up having to pass many objects to the constructor that could just be composed and built out with builder methods. That's where the real power shows up. Love your content. Great presentation. Would love to see more.

Thanks. Pretty nice explanation, subscribed

thanks a lot

Keep up the good work man!! Your channel is going to be epic one day 👍🏻👍🏻👍🏻

Its painful when you write code without semicolon 😨

good video, please keep up and do more videos. thanks

Interesting, thanks for this, but quick question - why no semi-colons? Are they not needed anymore in javascript?

Where is the director. I am confused. I have seen other tutorials where they use something called a director.

Very good stuff

Great video, I wonder if there is a way to implement builder like in JS with php, regardless the original way

Thanks for the great break down in this pattern! I love that your doing design patterns for JavaScript. Have you given it any thought on do this series using proto_types?

Great video !!! Thanks for sharing this knowledge !

so clean. Your videos are perfect little nuggets for beginners. Enough info to understand the "why" without getting bogged down in the weeds. Thanks!

This is so slick. Very nice.

Thank you :) Need more pattern please

Really useful video! But resolution options are available in the only 360p.

The first one is builder pattern. Second example is called "named parameters" , you can use it in classes and functions.

awesome thank you

What's the advantage of using a builder comparing to using setters directly in the user class? Sorry I didn't quite get it

Thank you for Video Kyle. I actually have a doubt if we can call any parameters for multiple times in the builder pattern?

So this is like the state Hook in React?

Thanks. Trying to learn Builder Pattern in Java, and found your video very helpful 🙂

Which theme is this in your VB Code I love it, plz name it.

Simple, useful and very clear. Thanks man for that amazing content!

thx from Russia..!

Really helpful. I was looking for python examples but the ones I found were making it bit too complicated, this was simple and precise.

Please tell me you work at google? You are damn good. Thanks for explaining this.

Great Explanation with examples! Keep it up, man!

cool...👍

Im sorry but this is not a classic builder pattern, you also have to implement a director class, and pass a builder object to it , then call construct() on the director and get product from builder

thank you

nice your doing so good man

Thanks

You are a Legend.

thank you so muchh

Hey you're posting Great Stuff man!! Thank you for that. Btw Can you show us how do you run your js files in browser? 😂

You should really use console.table() for these examples :)