Favour composition over inheritance. Separate what stays the same from what changes. As we are using a new operator, it's a program to an implementation not to an interface. We can use the factory pattern here. Right?

@@niwanshumaheshwari4534 using new operator doesn't mean we are programming to an implementation ; it's about how you're using it in relation to abstraction and interfaces. correct me if I'm wrong.

@@niwanshumaheshwari4534 Also you client should be the one who should initialize the class. You can inject your classes using types in static type languages and using type hints in python

thanks

nice

Thanks

thank you so much bro

Thanks Bhai ❤

Bro, do you have code of Observer Design Pattern of this lecture.

thank you, yes let's keep practising.

Did you make a comeback

😂😂​@@nigyban-theallrounder9016

bhai comeback hua?

bhai comeback hua ya nhi ?

Exactly

Thanks 👍

:)

Thank you. Pls also share it with your connections :)

Thanks Umang, really appreciate it.

Also continue in hindi always... its your USP... loved it

thank you

Thank you

Glad it was helpful!

Thanks

thanks a lot

thank you

Thanks

Thank you

tha

noted

Thank you, pls check my LLD playlist Arifur.

thank you

Totally relying on you guys:)

sure Amber

thanks Ravi

thank you

thanks

Thank you

thank Abhay

let me check the video Hardik and then i will be able to clarify your doubts. But one thing i can tell is this is design pattern video, so pattern defined in this, and class and their relationship will be correct as its well documented.

We are not instantiating the object , but just declaring a variable of that type. And then assigning the value.

Thanks 🙏

Do let me know as well, I have the same doubt :/

You should always go ahead with the LLD first, even some companies don't have this round explicitly but then it assumed you should know these principles already. Then you go HLD. For both of them see videos on a lot of problem use cases. You will be able to grasp these concepts well

Thanks 🙏

Thanks

Thank you

Hi Rahman, very good question. Let me try to elaborate: - Do we need to use all 3 types of patterns to make an end to end application. Answer is NO. Using Design pattern is not mandatory. You can build system without using any pattern and live with it if system is Readable, Scalable, Manageable etc. You dont need design pattern. Let say for solving one part of the system you need to use some pattern, you can use a pattern from any type not necessary to use pattern from all 3 types. - Single pattern for helping in Interview, thats a tough question, i would say that depend on what question you get in the interview, basics questions can be created through common design patterns like Factory,Structural. But for some specific questions like design logging system, design Notify system we need to know those patterns in advance or come up some clean design during interview itself.

@@ConceptandCoding thank you for clearing the doubts. So basically during the interview for any particular scenario, I need to start with a design pattern which will suit most with the basic requirements. And need to add any additional design pattern for any new type of requirements. Eg: If asked to create a parking lot system, and if the basic requirements are can have multiple types of cars Can have multiple floor Can have multiple entry exit I can start with something like an abstract factory or factory pattern. If by any chance we need to log these events, we can use singleton pattern. Correct me if I am wrong. Thank you once again for prompt reply.

Thank you

Thanks

Thanks

thank you

thank you

Hi Danish, i can definitely tell you are good in coding and DSA. And regarding LLD, there is no Level (which you can go deep). Level might be there in HLD where you can go deeper n deeper on one part of the design, like DB design, next level is RDBMS or No SQL then next level is Master slave then next level is Partitioning then sharding etc. But for LLD, its all about how good is your understanding with Objects, from the given problem are you able to identify Actors (objects), then what all features(member variables) it should have and then function. And how these different object interact with each others / what would be their relationship. Thats what Design pattern will help and to identify when and where which design pattern need to apply, that comes with experience or practice. Sorry for the long answer 🙂

​@@ConceptandCoding Hey Thanks for those kind words, I hear you and it totally make sense specially "identify Actors" and finally relationship , will take those input and start learning/practicing accordingly 🙏

this is because, lets assume, later on another functionality like display() will be added and it would be same for sport cars and passenger car and not in off road car, then we can create similar strategy for display and inject them in vehicle constructor. Adding more interfaces will not be a good scalable option with increase in features.

As you update and add new features, how many interfaces you will add and how many interfaces you will refactor? That is the reason we should not opt for this.

Glad you liked it

Hi, pld do check my LLD playlist, i have added many patterns and will add more soon

Thanks

Welcome

Glad it helped!

Thank you

I haven't added that, will add it soon

Thank you

No, for everyone function we can not create a new class. Else we will create another problem called class explosion. We can keep related functions in one class.

Thanks

Hi Naman, check Design Parking Lot LLD video, i have used strategy pattern there

@@ConceptandCoding thanks for reply I am just going through that video only😄😀

while both the Bridge and Strategy patterns involve breaking down hierarchies, the Bridge pattern separates abstraction from implementation, allowing them to vary independently, while the Strategy pattern encapsulates a family of algorithms, making them interchangeable. The key difference lies in their intent: Bridge focuses on separating abstraction and implementation, whereas Strategy focuses on encapsulating algorithms.

I have shared the gitlab link in my Channel home page only Vamsi.