What are the two most frequently asked questions for us? 1: WHAT IS in28minutes? ----------------------------------------------- I'm a great believer that if you spend 30 minutes every day taking a small step towards your dream, you will reach the top 5% of whichever career path you choose. And that where in28Minutes comes from. Spend 28 minutes a day learning something new :) 2: How do I learn about in28minutes Roadmaps? --------------------------------------------------------------------------------- All answers here - www.in28minutes.com/roadmaps Keep Learning Every Day To Your Success Ranga Helping 1 MILLION learners take their FIRST STEP into AWS, Azure, Google Cloud and DevOps!
I came here to understand SOLID principles as an experienced software professional that never picked up the buzz words but needed to pass interviews. I wasn't disappointed!
Finally I got consice and perfect definition of Dependency Inversion Principle : Functionality should be dependent on Abstractions(Interfaces) not upon concrete classes
When you give example of classes which are having multiple reasons to change then you should also give example which is having class with single reason to change.
In every single SOLID video, you guys have to take the shape as an example for showing the Open Close Principle. but in real life, it rarely happens this way. These by book examples typically wont work very well.
Its a good video for quick understanding, but im confused with Liskov Substitution Principle, i think it is the other way around, in wikipedia it is exaplained that the parent classes should be replaceable with the child classes and the programm should still work, but here you are saying or thats what i understood, that the childs should be replaceable by their parent and the programm or app should still work, then how it is?
Very good explanation, thank you. The example for Dependency Inversion can be extended to show different concrete classes inputted as param to copy method. Then, we can see that copy method can receive different concrete classes as long as they implement interface Reader or Writer. CMIIW
Your code in liskov substitution principle is wrong where is the inheritance between square and rectangle. Subtype should substitute supertypes. The idea in geometry is that a square is a special case of rectangle but this would cause problems you mentioned
I think its better to go back and understand what a principle does. A principle is just a high level guidelines to design software applications and do not provide an implementation details specific to programming languages. Now, dependency injection or DI frameworks is an implementation of that principle which is shipped as a product you can use as an extension when building applications and there is a lot you can choose from.
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
What are the two most frequently asked questions for us?
1: WHAT IS in28minutes?
-----------------------------------------------
I'm a great believer that if you spend 30 minutes every day taking a small step towards your dream, you will reach the top 5% of whichever career path you choose. And that where in28Minutes comes from. Spend 28 minutes a day learning something new :)
2: How do I learn about in28minutes Roadmaps?
---------------------------------------------------------------------------------
All answers here - www.in28minutes.com/roadmaps
Keep Learning Every Day
To Your Success
Ranga
Helping 1 MILLION learners take their FIRST STEP into AWS, Azure, Google Cloud and DevOps!
I came here to understand SOLID principles as an experienced software professional that never picked up the buzz words but needed to pass interviews. I wasn't disappointed!
Same happened with me..but it is actually helping to understand OOPS at more granular level. 👍
I think this is the best SOLID explanation available on TH-cam. To the point.
The best short video on SOLID that I have seen so far!
Finally some one explain solid principles and not just repeat what text book is saying
I paused the video in between to like the video and to thank you for explaining in such an easy way.
This is just perfect, been reading this from last decade but the way examples presented will make it last on my head forever
Best SOLID class I ever saw on the Internet!! Thanks!
This is best SOLID principles video till now. Explanation is to the point and good examples. Voice is good too. Thanks.
BEST 8 min spent.. to the Point.. Thank you!!
Dude, you are the first person that helped me make sense of the Liskov principle! Thank you!
Best video so far I have seen for SOLID principles
Finally I got consice and perfect definition of Dependency Inversion Principle : Functionality should be dependent on Abstractions(Interfaces) not upon concrete classes
When you give example of classes which are having multiple reasons to change then you should also give example which is having class with single reason to change.
Really it's very simple and easy to understand the concept, Thanks in28minutes.
I thought the topic was ambitious but you nailed it.
This video deserves an oscar!
thanks for teaching these concepts in an efficient way.
the first 4 principles are correct. The DIP example is very similar to open/closed
I was hoping you'd show a solution for your Liskov example. Great explanation
you explained that which example is not good for liskov principle, but you should show a good example also of liskov principle
best explanation of SOLID
Best explanation so far!
This is a clean explanation of clean code principles. Awesome!
Thank You for providing this crisp and to the point reference to the SOLID principles!!
Great explanation!! short and concise, understood solid principles so quickly
I have been asked this question in interview, now I am prepared after watching this video 👍
thanks , very crispy, especially the examples are really good , we need such examples for such design philosophies
Solid explanation.
Excellent explanation! Thanks!
Awesome work Ranga!!!
This is the best explanation I've seen in video OR print! Very clear and precisely explained, thank you!
Single responsibility does not means create new class for evry new task, we can say it is for ralated task
Superb explanation 😇🙌
When he explains he knows what the listeners are looking for .🔥
Bravo! Thank you. This was helpful :)
Awesome Explaination
Awesomely explained
Liskov substitution principle: Is it subtype must be substitutable for their base type or Super class must be substitutable for their subtype?
Simple explanation
Very clear explanation. ThanKS
thank you so much sir ... great explaination ...
Nice video and knowledge. Especially Interface segregation Principle and its example is awesome 🙌🏼👏🏻👏🏻
In every single SOLID video, you guys have to take the shape as an example for showing the Open Close Principle. but in real life, it rarely happens this way. These by book examples typically wont work very well.
Thanks for this!
the basics are very well explained here.
You can groom a tiger. Just be prepared to get eaten. You'd quickly turn from being a SOLID to MEAT!
Very clear explanation...
Will follow all your java videos
Really helpful
best tutorial
Nice examples
Very concise and enough to prepare for interviews ;)
very nice explanation with clear examples :)
thank you
Glad it was helpful!
Very clear explanation with relevant examples. ThankYou.
Very good video, explained SOLID principles so clearly in just a few minutes
Thank you.
Its a good video for quick understanding, but im confused with Liskov Substitution Principle, i think it is the other way around, in wikipedia it is exaplained that the parent classes should be replaceable with the child classes and the programm should still work, but here you are saying or thats what i understood, that the childs should be replaceable by their parent and the programm or app should still work, then how it is?
Nice, very simple and short video to brush up SOLID Principles. Thanks
nice explanation
loved it short and easy
Very nice. Short, crisp and informative. Keep it up!
Thank you sir.
coverd in time. you have readable blog?
Good explanation
You don't implement abstract class, you inherit from, you implement Interface
Thanks! Indian guy explained better than British ❤🩹
I don't understant Liskov again.. Is there any good resource with good example ?
Very good explanation, thank you.
The example for Dependency Inversion can be extended to show different concrete classes inputted as param to copy method. Then, we can see that copy method can receive different concrete classes as long as they implement interface Reader or Writer. CMIIW
This is sooo amazingg
He explained OCP as and DIP in the exact same way.
Yup, it is confusing a little !!
To the point explaination
Great 👍. Thanks
very useful and understandable
Indeed sir
Good job and Thank you Ranga!
Thanks a lot for this!
smart work in 8 minute ..please share video of design patterns type..
Awesome!💯🎯
Superb video, everything is explained with nice examples. Thanks.
good video
Is this a universal principle that is used with any system? If not what are other principles out there?
Can we use the example of OCP (as shown in video) in DIP?
Thanks a lot
Short and crisp 👌
Very good !!!
Cool! Very simple explanation! Thanks!
Liked, subscribed
Please upload more on solid principles
thanks
Your code in liskov substitution principle is wrong where is the inheritance between square and rectangle. Subtype should substitute supertypes. The idea in geometry is that a square is a special case of rectangle but this would cause problems you mentioned
thank you sir your explanation is fast smart and easy to understand . still have some problem with ocp but i think i know what it means a bit
Great video to refresh SOLID
thank you
Is dependency inversion principle same as dependency injection provided by DI frameworks like dagger, koin, hilt etc ?
I think its better to go back and understand what a principle does. A principle is just a high level guidelines to design software applications and do not provide an implementation details specific to programming languages. Now, dependency injection or DI frameworks is an implementation of that principle which is shipped as a product you can use as an extension when building applications and there is a lot you can choose from.
Isn’t it, square extends rectangle in liskov substitution principle. At 4:12
Thank you so much, really helpful :)
Great explanation... Thankyou!
Nice explanation!
Very clear and concise. Thanks
on the point great
Amazing class, thank you very much!
Great explanation and simple examples, thank you!
Cut and dry! Thanks a lot!
a ry good introduction of all SOLID principles in a very short video length...Thank you so much,Ranga :)