Here some problems I see: 1. 6:00 why Builder is an interface and not an abstract class. 2. The whole idea of Builder pattern is to allow clients to initialize the object with custom parameters as needed. The Director hides that complexity and provides a generic Build method. Meaning again the client is tied to the objects being initialized with specific params.

Liked and subscribed...

Great explanation in 10 minutes. Thank You.

great tutorial, thanks!

If we have a method createBurger in controller class in a web app and we need to create a burger we have to again put if else conditions to create different types of burger. Then what is the point to use this design pattern?

This video should get more views. absolutely top one. the information visualization and topics covered in a same story line helped me understand the whole process. Next, I am going to learn how the thread, scheduler are implemented in low level coding.

Thank you for this masterpiece

May I have these ppt for presentation in university😊😋

Java is dying and Oracle is killing it.

UNISA COS2614 students should be watching these videos. Very useful man

Thanks so much for explaining this...

I just enjoyed watching this video great explaination🤓

By hierarchical relationship sub class can not exist without super class it is same as composite aggregation ???

In Liskov's substitution is same to say: replace the child by its father or replace the father by its child? I see both ideas explaining this principle on the web

Thanks for the vid! But one small correction: In the state, you dont use the Phone as a variable, but as a parameter

Thank you so much

Wonderful explanation!

The hierarchy is • Operating System • Processes - Main process and child processes • Threads - Main thread and other threads • Tasks - Subroutines and Coroutines

I've just finished this playlist on design patterns, it's such a well done and structured resource for learning and reference. Thanks for these, really helped me learn quick!

This is great. Also check out DeltaJSON which can compare JSON objects with arrays or moving data, available as API and GUI.

Everything makes sense now thank u 🍬👌

Wonderful job. Cheers from Perú!!

high quality!

Amazing, clear information and quick delivery

Great series! Thank you!

Best video by far on the subject

Crisp and concise. Double thumbs up

load method should be final right? \

you mean var yeah not val ?

I think we have a simpler way for partition of an array: arr[] 1. Choose a pivot: p 2. Use two cursors L (left) that is the first index of array and R (right) is the last index. 3. Rule: while L <= R: 3.1. Increase L while arr[L] < p (loop until we find an element that is not less than pivot) 3.2. Decrease R while arr[R] >= p (loop until we find an element that is less than pivot) 3.3. If L < R: swap(arr[L], arr[R]) 4. Return L (partition point) Then we call quickSort(arr, begin, mid - 1) and quickSort(arr, mid, end). With "begin" is the first index of array, "end" is the last index, "mid" = partition point.

How do I do it without having to pull in a package?

All informations I needed, no less, no more, in five minutes. Thanks a lot mates

well, make a BurgerRegistry, register your burgers associated to a name. Give this registry to the Restaurant class. When a request comes, ask your registry to get the burger you want ! You just will have to register all your burgers as concrete implementations in a registry accepting all kinds of Burger instance... Now, my restaurant can deliver all kinds of existing burgers...

Superduper . Thanks a lot.

Excellent !! Thanks you !!

Excellent playlist of videos! They are helping me a lot today in 2024. Thank you very much for sharing this content!

9:40 This is exclusively for a mutable tree where you need the parent pointer on the node. If you want to create an immutable persistent version then you can't have the parent two way binding as you would need to touch every node in the tree during a mutation which would ruin the time complexity. Check out path copying for folks interested in an immutable persistent version!

waiting for videos where you apply these patterns in real backend applications with springboot :) please 😁

didn't get the idea how the algorithm understands that this is a word and not just a char sequence, may be I should watch it again

jesus fuck christ, one of the best explanation i've found about this on youtube. Thanks for taking you time and doing this man

Excellent information