From the examples it seems like Open Close principle is similar to Dependency Inversion principle and Liskov substitution principle is similar to interface segregation principle is it so ?
Hi Shabbir in INterface segregation you can extend DBInterface and FileInterface with in that it may remove the unwanted multiple inheritance in implementation class. Please share your thought on this.
Thanks for nice demonstration, however, I observe examples used while explaining one principle is violating other principle. To point out one, in Liskov Substitution Principle, Loan Payment class violates SRP with foreCloser method where it is supposed to do payment operations only. Correct me please, If I understand in wrong way.
Yes, they are very similar. The only difference i can think of is... L principle requires you to create separate interfaces which have relevant methods for your functionality. But in case of I principle, you split your interfaces into individual ones and can implement 'multiple' interfaces based on what you require. In case of L principle, you were still implementing one of the interface which is applicable to you. While in case of I principle, you are implementing multiple ones which are relevant to you.
In open-closed principle, how is the Calculator class going to be called to perform operation? Let's say we created an object of Calculator in main method, now how will we pass argument in calculator object to perform any operation?
Head to cutt.ly/spring_micro and use Coupon Code SUPER70 to get 70% off the course
Nice presentation. Got more clarity on SOLID design principle. My sincere thanks to you.
Thanks 🙏🏻
Thank you so much for these good examples, easy to understand solid principles now.
From the examples it seems like
Open Close principle is similar to Dependency Inversion principle and
Liskov substitution principle is similar to interface segregation principle
is it so ?
Hi Shabbir,
Great fan of your work! If time permits do a series on system design 🙂This would be highly beneficial
Thanks 🙏🏻
Hi Shabbir in INterface segregation you can extend DBInterface and FileInterface with in that it may remove the unwanted multiple inheritance in implementation class. Please share your thought on this.
Please also add API gateway and discovery design patterns
Thanks Shabbir, are you planning to do any video on spring security 5.7?, also love that this will have its own series
How about a video on Chain of Responsibility design pattern next ?
Great suggestion
Hi, nice video and understandable explanation with good examples ,Thank you. can you create spring boot playlist for beginners.
From the explanation it seems that LSP and ISP are same. Can you please post a video to demonstrate how they are different?
How these principles helpful in Component based architecture in React/Angular?
Thanks for nice demonstration, however, I observe examples used while explaining one principle is violating other principle. To point out one, in Liskov Substitution Principle, Loan Payment class violates SRP with foreCloser method where it is supposed to do payment operations only. Correct me please, If I understand in wrong way.
bhai this is one of the best tutor in the world ❤🔥🔥😘😘🥰😇
Thanks for your work. Please, explain the difference between L and I principles. It seems like the same.
Yes, they are very similar. The only difference i can think of is... L principle requires you to create separate interfaces which have relevant methods for your functionality. But in case of I principle, you split your interfaces into individual ones and can implement 'multiple' interfaces based on what you require. In case of L principle, you were still implementing one of the interface which is applicable to you. While in case of I principle, you are implementing multiple ones which are relevant to you.
Thanks, this gives me more clarification on SOLID. Do you have a public git repo for this?
I will create one and add in description
Thank you so much man, this helps sooooo much.
Glad it was helpful 🙏
Great video and easy to understand. Thanks!
Thanks 🙏🏻
In open-closed principle, how is the Calculator class going to be called to perform operation? Let's say we created an object of Calculator in main method, now how will we pass argument in calculator object to perform any operation?
that's what the 3rd param. for example: perform (2, 3, addOperation) -> return addOperation.perform(2,3).
Very useful and very informative. Really super video for learners.
please create video from BI publisher report with spring boot Rest API
Hi Shabbir, when we can expect the cicd pipeline in your course?
By weekend
@@DailyCodeBuffer Thanks A Lot Shabbir
@@DailyCodeBuffer can we expect complete core java course by you ?
Bro please provide code of all your tutorials in github
Hi Shabbir, Is there a code repo for all the code used in the tutorial ? And do you have UML diagrams for reference and revision. Thanks 🙏
Nice explanation..Can you pls share github link?
Thanks. Nice presentation
It's Liskov principle, not letsgo . Am I right?
Yes, UA-cam Auto Caption might have added that
Sorry about that
Thanks for informative video....can you make video on Design patterns
Planning on it
Thanks you for making informative videos!! God bless you
Thanks 🙏
Keep Supporting
Hi ,Can you pls provide git hub link for design patterns
Just Perfect !! Thank you
Glad you like it!
Thanks
Link of code repo plz ?
very very good video. Awesome!
Thank you so much sir👌
Thanks 🙏🏻
Very well explained thanks
Thanks 🙏
Nice presentation Shabbir bro..
Thanks 🙏🏻
Great job!
Thank you! Cheers!
"Single Responsibility Principle - Means that the class you create should only have a single responsibility" - DCB
"In order to understand what the recursion is the first must understand what is recursion" 😀😀😀😀😀😀
Very informative
Thanks 🙏🏻
Excellent
Thanks 🙏🏻
Love you
Awesome video
Thanks 🙏
Super bro nice video
Thanks 🙏🏻
nice
Thanks 🙏🏻
may be nobody told you this.. but keep your face in circle only... or at least don't zoom on you much. rest explanations are good.
Thank you for the feedback 🙏
superb bhaiya
Thanks
Excellent
Thanks buddy 🙏