Builder Design Pattern Explained in 10 Minutes. Easy to understand! code: github.com/selikapro/oop/blob... Join the Discord to talk to me and the rest of the community! / discord
The explanation is very detailed. Thank you. However I would pay more attention to the use cases (when and why do we need this pattern). And I would also use a different language such as Java, C# or Typescript in order to make it easier to understand for people that are not familiar with python syntax. It's also easier to understand what are the instances of variables with those languages.
Good points. I considered adding "when and why" to use the patterns but I felt the videos would be too long for the average attention span. The most recent video that I'm releasing later on goes into a bit more detail about when and why and it easily exceeds 20 minutes. Kind of need to play the balancing game. I think you make a really good point about the language and I actually almost used Java (I also considered Go) but I ended up going with Python because it's easy to read. But who knows, maybe I'll remake the videos for multiple languages. Not sure yet.
My understanding about builder pattern is use a predefined object inside director class and get the product of our choice Imagine we have a house, different preference of house by different people, instead of constructing a house of one’s choice, why not create a different type of house that are possible and use director to get the house. This saves time as well as avoid bloating of constructors.
If you could make one on Adapter pattern and Strategy pattern please. These confuse me a lot. Adapter - because i get confused with which needs to be wrapped - the examples around contribute more to the confusion. Strategy because it looks like a if-else which is more like a factory - though factory is a creational pattern and strategy a behavioral one
How is this pattern better than using the constructor? Perhaps I've not yet seen a real case where this would make sense, maybe if we're dealing with really big constructors with a lot of parameters? Idk
I can also see this as useful if the object's parameters are only given one at a time. You can then use build once all the necessary parameters are given.
I explain why you might use this pattern in the video. Both points about many constructor params and building individual attributes of the object at different points that you both mention are explained in the video. Please watch the whole video 🙂
This pattern comes to handy only when you understand the need. If you are concerned about why it is good replacement of constructors is that it strictly follows open close principle. Otherwise it’s all same tricks, it just saves you from modifying existing working class. I do not see other benefit. The client is happy that additional features didn’t interrupt writing flow.
For example I am working on a library for a communication protocol, I have to take multiple types of inputs and depending of those I need to build different type of messages, applying this made my code flexible because I decoupled creation from use and I was able to create different methods for different types of message objects. An alternative would be to create an abstract message class and have concrete implementations and use a factory method pattern, but due to the size of attributes I was repeating my self like crazy, that's why this pattern worked great for me in this case. This also comes in handy when working with protobuffs.
@@kantancoding not sure how youtube ranks videos. i guess by adding the language in the thumbnail would make your videos come on top once searched, because most of the design pattern videos are in java. Also you may add catchy captions, such as 'concept to code - so that you can code your way' etc. I just happened to have stumbled on this. now i keep searching if your new video has come on design patterns. Your videos on design pattern in python are the best which clarifies the fundament of the pattern definition and demonstrate the code with meaningful example. Honestly, this one was intuitively the best among all i have watched/read - and i had browsed a lot before coming here
@@chandrikasaha6301 Yeah the reason I didn't put Python is because you don't need to know Python to understand this video. I'm pretty sure that as long as you know any programming language you will be able to understand this.. But I always forget how language specific people are when learning. I was the same way in the beginning actually so not sure why I always forget this. I think it's a good idea. Thank you
why all similar explanations are explained by the example of dogs, houses and similar nonsense? Do the authors think that we, programmers, will not be able to perceive an example from a real design problem? imho, such explanations are suitable only for those who need to get an assessment at an educational institution
I really nice way to use this is for unit tests. If your class takes in like 15 params, you create a default builder for your happy path, and then can individually change individual fields to test your edge cases. happyPath = builder.build() InvalidZipCode = builder.setZipCode("INVALID_ZIP_CODE") IgnoreInvalidZipCode = builder.setZipCode("INVALID_ZIP_CODE").setIgnoreInvalidZipCode(true)
