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!

@priyanshusharma5989

5 ай бұрын

that Area method to loop Shape ArrayList should not be named as Area , it should be commulativeArea or totalArea , polymorphism is not needed for this method

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!

@mohdrasid6737

2 жыл бұрын

Same happened with me..but it is actually helping to understand OOPS at more granular level. 👍

How to learn Programming, Cloud, and DevOps? kzread.info/dash/bejne/iYeew6Snf7q3ZJM.html

Dude, you are the first person that helped me make sense of the Liskov principle! Thank you!

Thank You for providing this crisp and to the point reference to the SOLID principles!!

The best short video on SOLID that I have seen so far!

I think this is the best SOLID explanation available on KZread. To the point.

Amazing class, thank you very much!

Really it's very simple and easy to understand the concept, Thanks in28minutes.

Great explanation!! short and concise, understood solid principles so quickly

This is best SOLID principles video till now. Explanation is to the point and good examples. Voice is good too. Thanks.

Best SOLID class I ever saw on the Internet!! Thanks!

Very clear explanation with relevant examples. ThankYou.

BEST 8 min spent.. to the Point.. Thank you!!

I paused the video in between to like the video and to thank you for explaining in such an easy way.

Finally some one explain solid principles and not just repeat what text book is saying

This is just perfect, been reading this from last decade but the way examples presented will make it last on my head forever

Nice, very simple and short video to brush up SOLID Principles. Thanks

Very good video, explained SOLID principles so clearly in just a few minutes

Very clear and concise. Thanks

This is a clean explanation of clean code principles. Awesome!

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

This is the best explanation I've seen in video OR print! Very clear and precisely explained, thank you!

Cut and dry! Thanks a lot!

Thanks for the video, I have one question: insted of extending interfaces, is it better to have for example one "Animal" interface, with some common functions, feed(), communicate(), etc., and maybe some small other interfaces, for example: "Groom" with only groom(), "CatchPrey" with catchPrey()? Somehow I feel that by extending the interfaces around we would have a rigid structure at the end. Thanks a lot for an answer!

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

Very concise and enough to prepare for interviews ;)

Bravo! Thank you. This was helpful :)

I have been asked this question in interview, now I am prepared after watching this video 👍

Nice video and knowledge. Especially Interface segregation Principle and its example is awesome 🙌🏼👏🏻👏🏻

Cool! Very simple explanation! Thanks!

thanks for teaching these concepts in an efficient way.

Very clear explanation... Will follow all your java videos Really helpful

the basics are very well explained here.

best explanation of SOLID

Great video to refresh SOLID

thanks , very crispy, especially the examples are really good , we need such examples for such design philosophies

Great explanation... Thankyou!

Awesome work Ranga!!!

Excellent explanation! Thanks!

Great explanation and simple examples, thank you!

You can groom a tiger. Just be prepared to get eaten. You'd quickly turn from being a SOLID to MEAT!

Very clear explanation. ThanKS

I thought the topic was ambitious but you nailed it.

I like the video, however I would like to know what would be the best solution for the LSP problem you have explained in the video.

@Grempington

4 жыл бұрын

Both should inherit either directly from shape or from an abstract quadrilateral shape that does not have width or height, and have only their appropriate setters and shape data in their implementation Though it is a bit of a tricky example as a square is a specific type of a rectangle (if width and height are the same then the rectangle serves the exact same purpose as a square) Should there be a square class to begin with? It's debatable. Since their only difference is equal width and equal height there should probably simply be a SquareValidator for Rectangle and be done with it.

Best explanation so far!

loved it short and easy

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.

Short and crisp 👌

Thank you !

Is dependency inversion principle same as dependency injection provided by DI frameworks like dagger, koin, hilt etc ?

@meowaves

3 ай бұрын

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.

thank you so much sir ... great explaination ...

Good job and Thank you Ranga!

very nice explanation with clear examples :) thank you

@in28minutes

2 жыл бұрын

Glad it was helpful!

This video deserves an oscar!

Liskov substitution principle: Is it subtype must be substitutable for their base type or Super class must be substitutable for their subtype?

Thank you.

Awesomely explained

I was hoping you'd show a solution for your Liskov example. Great explanation

The best explanation thx

Thanks!

Thanks a lot for this!

Really well done. Thank you for making this video. Subscribed.

Is this a universal principle that is used with any system? If not what are other principles out there?

Thanks for this!

Awesome Explaination

smart work in 8 minute ..please share video of design patterns type..

Can we use the example of OCP (as shown in video) in DIP?

Nice explanation!

Very nice. Short, crisp and informative. Keep it up!

When he explains he knows what the listeners are looking for .🔥

is there a class where you are going in detail about these principles? with real world examples? I don't have interview, I just want to learn how to apply these and DRY in day to day development.

very useful and understandable

@yoopie6134

4 жыл бұрын

Indeed sir

This is sooo amazingg

Solid explanation.

Great 👍. Thanks

Thank you sir.

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

Simple explanation

To the point explaination

coverd in time. you have readable blog?

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?

best tutorial

Thank you so much, really helpful :)

Awesome!💯🎯

Superb explanation 😇🙌

I don't understant Liskov again.. Is there any good resource with good example ?

Nice examples

very usefullll!!

isn't dog should implement pet interface, not extend? correct me if i am wrong

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.

a ry good introduction of all SOLID principles in a very short video length...Thank you so much,Ranga :)

thank you

Good one sir!

nice explanation

Thanks a lot

Very good !!!

on the point great

Good explanation