I see some comments claiming code doesn't work...slight mistake..blah blah..but what more important here is the way how the things are explained....this channel needs more attention..you got a new subscriber
ok. That is an ASAP subscribe. This is EXACTLY the next level I was looking after reading all the beginners tutorials in programming and feeling completely stable. Thumbs UP!
Interesting, i read an article on DigitalOcean that suggested making the Game class have a private constructor and to make GameBuilder an inner static class. This way, the only way you can instantiate Game is to use the builder. Good video!
Nice video, thank you. I have question. With the builder pattern, how would we go about changing or updating a value. For example. Let's assume I made a Game object that did not have weather but later I want to add to the existing object later. How would I go about this with the pattern? Please also assume that the build method ignores the null check for weather. Let me know if the question is clear or not. Thanks for reading.
+Ersen Osman If I understand your question, I think you'd just add a setter method to change the weather. You can have a value set in the builder, and also set later as and attribute setter.
Is there any problem if I have more constructors? I mean... a Full constructor with all parameters, an empty Constructor and a Contructor with the builder approach?
Hey Deege, great video. Is it a good practice to have the builder class as "STATIC" inner class rather then it being "Non-Static"? What are the advantages to make the builder class static?
Awesome Explanation ! just subscribed and like the video. Thanks. Would be great help , if you could provide similar video tutorial on other patterns and principles as well .
Hi the video is awesome, thank you for your help. I can't find the source code from this episode on Github. Is there any chance you could send me the source code?
I have been creating a nested public static class Builder and inside and right away I make an instance of the parent class. Then my in my Builder I just set the instance fields and in the Build I just return that instance. I find it easier than having my constructor take a Builder builder. I am new to Java coming from OO Python and I gotta say this language really sucks. I find everything to be a huge pain to work with to do even basic things.
Maybe I discovered a slight mistake here. 4:16 All the properties of the GameBuilder class are private 4:44 awayTeam = builder.awayTeam; homeTeam = builder.homeTeam; etc... Wut?
Actually no, that's correct. You usually want your attributes to be private, and only accessible through getters and setters. The code sets the variables in the constructor, where they are accessible. You might check out episodes 27 (th-cam.com/video/JK7ltJLCgqM/w-d-xo.html) and 28 (th-cam.com/video/eQCXrNBD0aQ/w-d-xo.html) where I talk about that a bit. If that doesn't help, let me know and I can create another video on it. Thanks!
Hello there, Deege U. Thanks for the reaction, but that is not quite what I meant. What I mean here is that all the properties of the GameBuilder class have been set on private, that is indeed a good move. Although... In the Game class, all the properties are used as though they were public properties. I could be wrong, but wouldn't this be correct? awayTeam = builder.getAwayTeam(); homeTeam = builder.getHomeTeam(); etc...
Ah I think I see what you mean. The GameBuilder attributes are private, and would not be accessible in the Game class. Yes, that's an error. :) Doh! Good catch!
So I haven't gotten around to filling in the source code for the Java tutorials, mostly because the code would just be toy examples. But I do have some code using the builder pattern for an upcoming tutorial. There's other code surrounding it, but you can find the builder pattern here. github.com/deege/deegeu-quizzer/blob/master/src/main/java/com/deegeu/trivia/model/TriviaQuestionBuilder.java
I realize that the train left the station a while ago. Nevertheless.... On appox. 4:27 the following is painted public Game build(){ if (homeTeam ==null){ throw new IllegalStateException("No HomeTeam"); } if (awayTeam ==null){ throw new IllegalStateException("No AwayTeam"); } ............................................................................................ ............................................................................................ ........................................................................................... return new Game (this); } The method build of type Game belongs to the GameBuilder class, correct? And, as name suggests, i have expected to see here the actual build, i.e. Game game = new Game(); game.homeTeam(ht); game.awayTeam(at); ................................... ................................... return Game But the method does not build anything, just provides some validations What am i missing? Probably everything :-)))
You claim that the builder pattern should only be used for large complex classes. I see your point but the builder pattern is supposed to help you in case your class grows very large and you keep adding more variables to the constructor. The way to avoid future problems for people accessing your code is to use the builder pattern from the start. :)
Anders Rapp I started in Java recently and after my first time trying to remember the order of a 10 arg constructor I decided builder is the only way to go here.
I dont think you ever showed a GameBuilder.build method. You showed a Game.build method but not a GameBuilder.build method. But after calling all the build methods you recommended calling .build last. So im just going to a assume GameBuilder.build looks something like the Game.build method
one of the best java tutorials ever happens on youtube. I do respect on the way he explained with a real-world example.
Think I finally get it because of the explanation on previous videos. Proper teaching.
I see some comments claiming code doesn't work...slight mistake..blah blah..but what more important here is the way how the things are explained....this channel needs more attention..you got a new subscriber
ok. That is an ASAP subscribe. This is EXACTLY the next level I was looking after reading all the beginners tutorials in programming and feeling completely stable. Thumbs UP!
Glad it helps! That's what I'm shooting for. Intro that goes beyond "type this".
Interesting, i read an article on DigitalOcean that suggested making the Game class have a private constructor and to make GameBuilder an inner static class. This way, the only way you can instantiate Game is to use the builder. Good video!
Thank you sir im so stupid so im glad i have people like you to help me
crisp and to the point thank u
Amazing tutorial. Why aren't you more well-known?
+Daniel Choi Thank you! Not sure? Probably because I've only been doing tutorials since April?
Subscribed! This was by far the most concise explanation I have seen.
This video is a blessing, thanks (from Italy 🍕)!
I really hope you are having (or you have had) the succes you are looking for (on TH-cam, and/or shool/university as a teacher); you deserve that.
Thank you so much. You always explain the concept clearly. please never stop making videos.
Really enjoyed this, easy to understand and follow. This really helped me understand the builder patterns used by the Android Pay API. Thank you!!
+Sergio Angel Glad I could help! Thanks for watching.
best one on builders! Thank you!
Amazing tutorial!
Awesome tutorial! Focused on particular problem and it's solution.
+Santosh kumar Dash Thank you!
once a great explanation always a great explanation .. even after 5 years :)
very good explanation.
Thanks for the video. One thing to note here is that we create an Instance or Object of a class, not creating a class.
Nice video, thank you. I have question. With the builder pattern, how would we go about changing or updating a value. For example. Let's assume I made a Game object that did not have weather but later I want to add to the existing object later. How would I go about this with the pattern? Please also assume that the build method ignores the null check for weather. Let me know if the question is clear or not. Thanks for reading.
+Ersen Osman If I understand your question, I think you'd just add a setter method to change the weather. You can have a value set in the builder, and also set later as and attribute setter.
Is there any problem if I have more constructors? I mean... a Full constructor with all parameters, an empty Constructor and a Contructor with the builder approach?
Thanks for the awesome explanation.
Awesome! Loved it, just subscribed and like the video. Thanks.
Thanks for that nice explanation!
great tutorial!! greetings from Mexico.
+lluuii fre Hola! Thanks and thank you for watching!
Thank you
Hey Deege, great video. Is it a good practice to have the builder class as "STATIC" inner class rather then it being "Non-Static"? What are the advantages to make the builder class static?
nice thanks
Thank you, very clear.
+Isay Arenas Soto Thanks for watching!
You are awesome. Subscribed.
Awesome, thanx!
good video, tx
Awesome Explanation ! just subscribed and like the video. Thanks.
Would be great help , if you could provide similar video tutorial on other patterns and principles as well .
I had planned on doing pattern videos, but haven't got around to it yet. Hopefully some time this year?
Great video. BTW can you provide us with a tutorial how to use builder pattern extending a class, please ?
cool tutorial!
+ibanezsindrome Thank you!
great video.... :)
+Jeet Parmar thanks for watching!
Hi the video is awesome, thank you for your help. I can't find the source code from this episode on Github. Is there any chance you could send me the source code?
+Bartosz Prażmo I've fallen a bit behind on the source code. I'll try to get that shored up this week. Sorry about that.
That doesn't quite work for me. In the method Game build() an error pops up saying that the constructor for Game is undefined
It really awesome..:)
+prem raj Thank you!
I have been creating a nested public static class Builder and inside and right away I make an instance of the parent class. Then my in my Builder I just set the instance fields and in the Build I just return that instance. I find it easier than having my constructor take a Builder builder. I am new to Java coming from OO Python and I gotta say this language really sucks. I find everything to be a huge pain to work with to do even basic things.
awsome !
Maybe I discovered a slight mistake here.
4:16 All the properties of the GameBuilder class are private
4:44
awayTeam = builder.awayTeam;
homeTeam = builder.homeTeam;
etc...
Wut?
Actually no, that's correct. You usually want your attributes to be private, and only accessible through getters and setters. The code sets the variables in the constructor, where they are accessible. You might check out episodes 27 (th-cam.com/video/JK7ltJLCgqM/w-d-xo.html) and 28 (th-cam.com/video/eQCXrNBD0aQ/w-d-xo.html) where I talk about that a bit. If that doesn't help, let me know and I can create another video on it. Thanks!
Hello there, Deege U. Thanks for the reaction, but that is not quite what I meant.
What I mean here is that all the properties of the GameBuilder class have been set on private, that is indeed a good move. Although... In the Game class, all the properties are used as though they were public properties. I could be wrong, but wouldn't this be correct?
awayTeam = builder.getAwayTeam();
homeTeam = builder.getHomeTeam();
etc...
Ah I think I see what you mean. The GameBuilder attributes are private, and would not be accessible in the Game class. Yes, that's an error. :) Doh! Good catch!
So do we need to put it inside the game class or what?
No use getters instead of directly referring to variables
I really wish I had the source code for this. I'd like to get in the habit of using the builder pattern than chaining constructors.
So I haven't gotten around to filling in the source code for the Java tutorials, mostly because the code would just be toy examples. But I do have some code using the builder pattern for an upcoming tutorial. There's other code surrounding it, but you can find the builder pattern here. github.com/deege/deegeu-quizzer/blob/master/src/main/java/com/deegeu/trivia/model/TriviaQuestionBuilder.java
Thanks!
Starts at 1:10
I realize that the train left the station a while ago.
Nevertheless.... On appox. 4:27 the following is painted
public Game build(){
if (homeTeam ==null){
throw new IllegalStateException("No HomeTeam");
}
if (awayTeam ==null){
throw new IllegalStateException("No AwayTeam");
}
............................................................................................
............................................................................................
...........................................................................................
return new Game (this);
}
The method build of type Game belongs to the GameBuilder class, correct?
And, as name suggests, i have expected to see here the actual build, i.e.
Game game = new Game();
game.homeTeam(ht);
game.awayTeam(at);
...................................
...................................
return Game
But the method does not build anything, just provides some validations
What am i missing? Probably everything :-)))
You forgot to implement the Director class. Without the Director class the Client is going to be tightly coupled to the builder.
You claim that the builder pattern should only be used for large complex classes. I see your point but the builder pattern is supposed to help you in case your class grows very large and you keep adding more variables to the constructor. The way to avoid future problems for people accessing your code is to use the builder pattern from the start. :)
Anders Rapp I started in Java recently and after my first time trying to remember the order of a 10 arg constructor I decided builder is the only way to go here.
fucking legend!
I dont think you ever showed a GameBuilder.build method. You showed a Game.build method but not a GameBuilder.build method. But after calling all the build methods you recommended calling .build last. So im just going to a assume GameBuilder.build looks something like the Game.build method
interesting. thanks