Java Builder Pattern Explained in 3 Minutes

Рет қаралды 14,823

Jack Hodkinson

Күн бұрын

Пікірлер: 44

@jack.hodkinson 6 ай бұрын

What topic would you be interested in learning about next?

@PilarczykM 4 ай бұрын

Any design pattern will be valuable 🤗

@Play_Streams 6 ай бұрын

I love this no-fluff approach. Simple and straight to the point. Sub +1

@jack.hodkinson 6 ай бұрын

Thank you!

@bcampera 4 ай бұрын

Thanks for the explanation. I feel like this is only needed because of modern features that other languages have and Java doesn't. I had some experience with Dart and I loved its named constructors and named mandatory and optional parameters. I will never understand why this doesn't get added to Java

@DamLee88 6 ай бұрын

also lombok @Builder makes the job easier, thanks good video

@jamessinnott8798 Ай бұрын

Thanks for the video. Explained very well compared to some of the other tutorials I've seen online.

@vladtudorache2483 Ай бұрын

Your best video.

@IvanToshkov 6 ай бұрын

Nice. I normally prefer to use runtime checks and exceptions, but for more complex objects the multiple interfaces may pay up? Here's an idea for a followup video: You have three classes: an abstract Base class and classes A and B which extend it. Create builders for them without code duplication.

@maximschott1300 Ай бұрын

Thanks a lot for this video! +1 sub, so don't stop recording the interesting videos :)

@DominikusHerzberg 7 ай бұрын

Wow, very impressive explanation and coding style. The channel I was looking for but didn't know existed. Thank you very much!

@returncode0000 8 ай бұрын

I like your explanations so much! Always on point and really helpful, great job 👍

@jack.hodkinson 8 ай бұрын

Thank you :)

@softwaretactics1536 5 ай бұрын

It is so mind boggling that you have imbibed so much into a 3 minute video!

@mrindian7422 8 ай бұрын

Can you pls create complete playlist for along with real time project in Java 8 for collage student

@jack.hodkinson 8 ай бұрын

Working on it! I have a live coding project here, where I implement an ArrayList in real time kzbin.info/www/bejne/hmOzXo2Lq66mkK8

@mrindian7422 8 ай бұрын

@@jack.hodkinson Thank you very much

@vib7777 2 ай бұрын

Awesome!! Subscribed

@mrindian7422 8 ай бұрын

Love the way you think ❤

@sobeck6900 6 ай бұрын

WOW, explained more in 3 min than some books...

@tylerbakeman 6 ай бұрын

Coding setters as chain-able methods is always satisfying: instead of- void setX () { … } using- ClassName setX() { … return this; } so you can theoretically: object.setX( v1 ).setY( v2 )… The only issue is if the setter’s aren’t final (returning a value other than this)- setters should probably be final anyhow (unless you have some sort of EventDispatch system).

@Mirage2020 5 ай бұрын

Java seriously needs to consider adding support for named parameters. There is just too much one needs to to in order to have the same functionality as python, dart and kotlin named parameters (it would also help a lot with deconstruction patterns, which they are trying to get good using the new proposed "with" keyword

@terrytorres5026 6 ай бұрын

Wholy crap,then we wonder why coding is overcomplicated and breaks when new releases of Java come out.

@PrasantaBarada-t7s 7 ай бұрын

I am your 1000th number Subscriber

@jack.hodkinson 7 ай бұрын

Thank you! Welcome

@prodevops6271 7 ай бұрын

Love it and subscribed after watching fist 15 seconds of this video.❤

@pas_pantou 5 ай бұрын

You can use also a Record class, the fields in a record class are immutable as well.

@noelgomile3675 6 ай бұрын

Would this be needed if Java had named parameters?

@jack.hodkinson 6 ай бұрын

Good question. Not really!

@dentjoener 6 ай бұрын

I always tell people that builders are just shitty excuses for named parameters. I tend to shy away from them because I hate them with a passion. Use smaller objects that can be composed into larger objects, link this with some domain driven design (a name might be a string, but an Email sure as hell shouldn't be), and there's way less issues. Also static factory methods >>> constructors.