1.1 Liskov Substitution Principle (LSP) with Solution in Java - SOLID Principles of Low Level Design

this is one of the important SOLID principle. And covered its both Problem and Solution

[ankitgoyal]

Youtube and people like you have made life easier, thankuu.

[Ricky-jrio]

An excellent explanation of Liskov's Substitution principle. I work primarily with python and javascript, and your explanation really illustrates well why typescript and type hinting in python are necessary to avoid errors.
Thank you very much.

[CanadaKeBhai]

Best example of Liskov's substitution principle

[nitigya]

This brings the point when to ditch Inheritance over Composition. Like how Abstraction/Inheritance brings coupling along with itself. Though, both Inheritance and Composition will have it's own pros/cons. Amazing playlist!

[anuraggupta]

One suggestion - hasEngine could have values - true and false. So instead of returning null, we could have returned false, and it would not break.
For this example, we could have taken something like engineType instead of engine. In that case, cycle will have to return null.
PS - I am new to these topics. Please correct me if i am wrong 🙂

[rajugoud]

This is the perfect Explanation of this principle, i watched this principle in paid courses, but this is the perfect explanation

[SushilChauhan-zq]

No one explained like you this solid concept..thanks

[ashishgoswami]

Awesome work ! I have been working for a while but you cleared concepts with examples!

[aishwaryas]

The solution proposed seems to be similar to Interface Segregation principle with the only difference being we use classes here instead of interfaces for segregation. Thanks for the explanation.

[SuyashD-cdwr]

Beautifully explained !!! keep up the good work !!!

[pavanls]

One more thing that comes into mind is separation of behaviours. We can set up behaviors as interfaces and select class can implement that interface while the rest need not have to. (Learnt this through an example in Head First Design Patterns) Shreyansh Jain, correct me if I am wrong. With this, we don't have to create more classes.

[dpynsnyl]

very nice explanation!
can you also add similar video explanation for all the other principles? This is a rock solid video, I don't think I will forget this easily.

[shubhammanecr]

Amazing... thank you for such clear explanation!

[shawkiahmed]

Good example to understand. thanks for your efforts

[saiakhil]

I think there is a slight conceptual mistake in the start of the video.

In the video, you mentioned that for a parent p, and child classes c1, c2, and c3, LSP says that parent *p = new c1should not break the behavior when c1 is replaced by c2, c1 is replaced by c3.
However, my understanding is that for the same scenario, in a code, if you use c1_object.setSomething() or c2_object.setSomething() and if you have a parent object, the code should retain its behavior if you change c1_object with p1_object.

Please correct my understanding if it's wrong.

[rohitvathumilli]

Hi Shrayansh,

1) The vehicle class, does it follow a single responsibility principle.
2) What if I return false instead of return null for the bicycle class, does it follow LSP

[gurupreetsingh]

In side bicycle u could return false instead of null ... Why returning null .. returning false can solve the problem..

[himanshukashyap]

Can we get the slides that you are sharing in your videos?

[shashankcool]

Nicely explained with help of example 😊

[OffRoadEngineerVlogs]

Nice information brother 😊 keep sharing