Play the video in 2x speed then you'll be learning SOLID in 10 minutes

0:00 Introduction 0:51 Find problem with existing code 1:36 S = Single Responsibility Principle 4:05 O = Open Extensions, Closed Modifications 7:09 L = Liskov Substitution 9:43 I = Interface Segregation 11:31 D = Dependency Inversion Great explanation with a simple to understand example. Amazing videos as always.

For Interface segregation principle; I think we shouldn't create a function (that sometimes needed and sometimes not) - printLogs() function in this video - inside the same interface, We should create another interface and declare this function in it and if we need this functionality we can implement this interface and plus other interfaces like FileLogger interface in this video

finally , now i understand why interfaces are so important ,I struggled so much to find reason to use them , Thank you philipp

In example for open/closed, you treated the FileLogger class as being completely closed. Your CustomFileLogger was effectively another implementation of a FileLogger interface. It is ok to add new functionality to the FileLogger class, for example adding another function called timestampedError(), as long as you do not change the logError() function it adheres to the open/closed principle. All existing consumers of FileLogger will work exactly as they did before. For your example of Liskov substitution, the CustomErrorLogger class does not violate Liskov substitution. All instances of FileLogger can be replaced with CustomErrorLogger and will work exactly the same. This is because all calls to logError() will still go to the base FileLogger via inheritance.

Been binge watching all your recent videos. Amazing Android content 👏🏽 👌🏽

awesome man. I didn' like you previously when seen on interviews but Now addicted to how you teach and how humble you really are.

Thankyou Philipp, your way of explaining the issues through examples is just amazing. Thankyou for this great video.

Great video Philipp, would be awesome if you would cover more of these advanced topics. Keep up the good work!

Vielen vielen Dank lieber Philipp für diese tolle Erklärung. Du hast da wirklich ein Talent solche Dinge sehr einfach für jeden verständlich zu machen. Liebe Grüße aus Österreich.

This is literally one of the best channels out there. I can’t believe that I only found it now. I love the videos. Keep them coming! P.s- would love to see a video about Alarm manager in Kotlin! Looking for such a video for a while.

Experience is so freaking important!. 6 months ago, i saw this video i didnt understand anything of it. Now i understand everything! Because without knowing, i used all of this on my job, day to day on Android. Excelent! Now going for theory behind design patterns

You have such a nice way of explaining things brother. Keep making these videos please. Thank you.

Just the thing I needed. Surely will start using all these principles in my future projects.... Thanks bro...

I watched this video after watching your multi module course. So clearly explained .. I clearly understand why you inject abstractions using hilt instead of concrete implementation ..... Thank you so much Philip

Thank you so much dear philipp for record this courses , I just wanted say i love you ❤️😘

Thanks for this video man!, Big fan of your channel

Simplest and best example with clean examples just like your clean codes @Philipp ! Awesome :)

really the most informative explanation of SOLID principles. appreciated and thanks a lot man:)

This is simple AF , nobody showed this important principle with this level of simple and easy examples ! Take a bow @Philipp

Keep making such videos.👍 It truly helps a lot.😌 Thank you 🙏🙂

thanks' a lot Philipp, appreciated your efforts

Thank you so much for clear explanation of SOLID 🙏

I got goosebumps when he said, "This changes the entire implementation in one line of code. 🦋"

This is a most important video in the internet for devs today. It's not easy to explain this topic the way he did. Kudos @Philipp

Great content. You made it clear for me. Thank you so much. . . . Thank you so much.

The best explanation I have ever seen. Great job

Thanks a lot for that awesome explanation!

I think a more appropriate example of Liskov substitution principle would be if an overriden function were to do something unexpected and contrary to its implementation in the base class. This can be shown with a base function that changes the state of the class which is overriden by a function that doesn't call the super method. The example provided doesn't break this principle. I liked the other explanations.

Great explanation man! Thank you!

Kudos Philip. This explanation was easy to grasp

Philip God bless you soooooooo much.... i can't thank you enough

For the optional interface function, you could also do = Unit instead of the empty function braces.

I like how you explain complex things so easy👍nice

Thank you for the explanation I learned something new today

The video we didn't ask for, but really needed..

Best video about SOLID I've ever seen

Well done video. Just pay attention to interface segregation. Interface segregation does not mean that clients do not need to implement the entire interface. It means that you should segregate different functions under several interfaces, and then it's up to the client to decide which interfaces to implement. I don't think the example here was demonstrative of interface segregation.

This videos was so helpful. Thank you

This guy is really good.... Keep it up bro

I finally understand them now, I faced the same problem when searching them online...very hard to understand. This was waaay easier to understand. Thank you!

I would've killed for this video when I first started learning Android and programming; Thank you.

So realy clearest explanation ever and simple practical Thank you Philipp

This is by far the best SOLID video explaining these complex SOLID software principles !! Thank you for this amazing content !!

Thank you it was very simple and easy to understand

This is really helpful,some tutorial only targets output without considering clean code,thanks Philipp

Nicely and simply explained

Thanks for the explanations with easy examples 👌👏

thank you very much , this is really awesome

Do we need to remove dependency on concretion of FileLogger class? For "I" principle you can split your interface in several interfaces. Thanks for video! ❤

This guy does it again!!! Nice explanations.

great material, very helpful, thanks !

Thanks. Very good explanation.

Thanks bro!

Hey Phillipp we need more videos on clean architecture, if possible please make a playlist on it. I will buy that playlist if it is paid but please make that playlist

Please make more videos like this !

Nice explanation on very complex and ambiguous topic. 👍👍 Plus i think we can do diff approach for interface segregation instead of giving default implementation.

Thank You bro

Thanks Philipp

Thanks philipp

Sir, u are the best!

For the open-closed principle, would you then be violating it if you provided a default parameter with the file path name, so that one could change the output location without extending the original class? Not sure if that's what you mean by closed to modification

I always enjoy your videos. Would u do one video on adding time and date in an android studio app

Thanks buddy

need to watch some more time. Thanks a lot

This is a good tutorial to me thank you.

Great explanation

thank you !

thanks for this topic Really thanks :)

Awesome continue plz.

Brilliant content

Very good video. One question regarding the Open Closed Principle: If I would create method for changing the path e.g.: open fun getPath(){...} Does this violate the principle?

saw videos about this topic and this helps me to understood it better. easy to undertand also for stating with solid and why use it half of the video after that i lost

awesome man👍

Perfection!

Hi!) I am from Russia and I am learning English to find a job in another country. You have good English I understand almost everything and your videos help me to learn the language))

Amazing!

After watching this last night I went back and re-watched Bob's playlist on clean code... outstanding! Then today in a long term project interview (We interview internally for projects) I was asked, 'what are the SOLID principles of good software engineering?' I played it cool, .. 'fools, little do you know Phillipp just schooled me on this shit' ... barely had the words come out of my mouth when the hiring manager said "wait you know Phillipp?" ;) Joking aside, the synchronicity is insane man, thanks so much for everything!

One of the best

Perfection

Can you please make video on Important design patterns for Android developers? Thanks in advance.

Thank you.

Superb!!

Really amazing video

Amazing content

I love this!!!

Awesome video!!

You are the best 👌

Bro, you are my new superhero, much much better than any other fictional superhero

lovve this

Amazing video, I have studied the SOLID principles and I have never understood them so easily, congratulations, greetings from Caracas, Venezuela

The thing that I liked about the video was not wasting my time to learn this SOLID buillshit. Thanks for summarizing.

You got some perfect communication skills

Thanks boss

Hi Philipp.... Could you please do a video on How to use Ktor on an Android client...

Can you please make medium scale app with clean architecture so we can practice on it.

Thank you!

thanks, it looks very easy to understand. Do you have any video about customizing views in android?

do you have an example of project with clean arhitecture?

grateful :)