► Get NordVPN exclusive deal here: nordvpn.com/amigoscode Try it risk-free thanks to their money-back guarantee! ► Grab your copy Clean Code copy here: amigoscode.hypg.es/amzn/clean-code ► Git Repo with examples: amigoscode.hypg.es/github/amigoscode/solid
Please make a video for Design patterns, as it will be beneficial for all developers. Thanks for your effort in bringing useful content to the community. Highly appreciated!
SOLID is a must know skill in OO development but I think we should be willing to modernise it and make it fit in 2022 when industry is moving towards functional coding. I’m a 20 year c# vet and do full solid on most projects but it’s hard to justify the abstractions for smaller projects. You end up with too many single method classes which can be functions instead.
Why does it matter if you have a single function or a single class with a single method? You're gonna have more files true, but still I dont see a problem here.
@@ivanvelinov4630 Overhead, both In computer and cognitive sence. Besides it is unnatural to put everything into its own box. Generally it is easier to spot a thing put into a bigger box, with many other things, rather than if everything, no matter how small was put into its own box, even if there is a label on each box. It's mentally draining, and the biggest nonsense of OOP to me, besides it is never used on big real life projects. The same with the modern notion of microservices. We are not far away from the time, when a new "breakthrough" in the programming would be ”discovered” in the form of a revolutionary notion for “macroservice“ (highly sarcastic here) as it is functional programming now. Something old, then forgotten in favor of the new hype, and then rediscovered as something “revolutionary" (sarcasm)
I really missed Amigoscode, I can't believe he still can take his time to share these incredible resources and knowledge during this fasting period, thanks Nelson 🙏🙏🙏
Great video! About the Liskov Substitution principle, although your explanation was right, the description should be exactly the opposite: every base or parent class should be substitutable by its derived or child classes. So, taking your example, if we have: Shape shape = new Shape(); shape.area(); in our code, we should be able to substitute the first line for: Shape shape = new NoShape(); but this would throw an exception, so we don't fullfil this principle. On the other side, if we have: Animal animal = new Animal(); animal.eat(); We could substitute it for: Animal animal = new Dog(); and it would still work as dogs have to eat. Hope that makes it more clear.
Also, please correct me if I'm wrong, he didn't have to create a new class to demonstrate LSP. The fact that he has a function that accepts "Shape" and it works even when it's supplied with objects of different shapes (Square, Circle, etc), that in itself obeys LSP because all of those are derived from "Shape".
I've been working as a software engineer for 2.5 years and do my best to obey the SOLID, this is by far the best explanation video of all the principles. Usually the interface segregation and liskov were not explained or ignored in case of languages like Ruby ( my first job / 2 years). Kudos man
Hi Amigoscode, thank you for the great video, however one thing to notice: I might be wrong, so feel free to correct me: The single responsibility is not about having a single purpose, but rather about having a single customerbase "single actor/purpose" whom the class/functionset is being programmed for. The functions should not be shared amongst different stakeholders like the finance team and the HR team in a company that both need a way to calculate the salary of a person - they should have different codebases for that because they are different actors. The principle of having a function do only one thing is not part of the Solid Principles of Uncle Bob, even if it is a very wise thing to do. (Read more in "clean architecture" by uncle bob.)
This is probably the fourth or fifth SOLID video I’ve seen since being introduced to the topic and, while they have all been informative, yours sunk in. Thank you so much for this. New Sub!
This is one of most important topic (and design patterns) that every developer should learn to write better code. I've met experienced developer who didn't know about these subjects and it's so unfortunate. Thanks a lot 💪🏾
Huge respect to people who know Java. It has been kinda hard for me to get into the language but this was extremely helpful!! But once again huge respect to people who can write clean java code while keeping all these in mind, just blows my mind.
Thanks for the video! One small point, I think it will be great vs run app each time, create few tests and run this test to show in own example that you like tests and how it is easy to work with tests.
I, m reading articles about SOLID principle recently. This video really helps me upderstand how to implement this princople. Your videos are awesome. Thanks from Taiwan!!
Hi Nelson, I'm new here, with no background of Computer Science, and your videos helped me a lot to understand the base of Java, right now I'm following an acreditate course, I would love if you can do videos about Generics, and explain Threads and Stream and Lambda, more understable for a begginer! We really love you! You are a good menthor and teacher! Bless!
It took me some time to understand Single responsibility. Each class can and should have more than one method, how do you do for them to have only one responsibility. The answer lies in "reason to change" as far as I know. Soo you should ask yourself what would make your code to change, like csv to json or saving in a file or a database or a queue.
Many thanks to you. I'm preparing for a interview and I just forgot all the definition of SOLID principles(event using some of them), and your video helped me a lot to refreshing my memory.
The SOLID principles are something I struggled with to abide by early one in my career and struggled walk explaining in interviews. This has definitely helped remember some examples and helped my understanding, cheeers! :D
Hello, sir! I want to thank you very much, for the tutorials and the work you are doing, and the effort you put in these youtube videos. Thanks to your tutorials, here in this youtube channel, I managed to land a job as a Java developer. Never give up guys! Hard work pays off!
Excellent tutorial! This explanations about SOLID principles would have been so precious to have at the begging of my career, I really hope it can help others in their beginning! For me it was excellent for refreshing knowledge!
The last is just waaw and it's used in the most framework especially in Spring framework, thank you so much, this will help me a lot to become a better developer 😎
Thanks dear brother may ALLAH accept your duaa, fasting, and prayers :) SOLID PRINCIPLES ►IP Single Responsibility Each class should have only one sole purpose, and not be filled with excessive functionality ►Open Closed Classes should be open for extension and closed for modification. In other words, you should not have to rewrite an existing class for implementing new features. ►Liskov Substitution This means that every subclass or derived class should be substitutable for their base or parent class ►Interface Segregation Interfaces should not force classes to implement what they can't do. Large interfaces should be divided into small ones. ►Dependency Inversion Components should depend on abstractions, not on concretions.
Kind suggestions for future videos: Live stream with interview questions that we try to answer A video about concepts that every junior developer must know with examples like this video
AleykumSelam Mashallah brother the cleanest explanation that can be found ever! Finally everything is in place on SOLID principles. I appreciate and strongly recommend it.
Much clear, but I have a question that why didn't you make the ThreeDimensionalShape interface inherited from the Shape interface? Is the interface inheritance an unusual practice, or there was another reason?
Iam wondering if there is a specific reason why you are using the Object class instead of Generics? For example in: public int sum(List shapes) {...} -> why not do this instead: public class Areacalculator { public int sum(List shapes){...} then you wouldnt have to bother about typesafty afterwards. but iam relatively new to OOP so please enlighten me if iam mistaken.
Hello, thank you for this well explained reminder. Just a little remark regarding the video format: can you reduce a little bit the size of your camera so we can see the whole code in your screen. Not that i don't want to see you lol but just for confort. Again thank you very much for all your work my friend. Salam.
Fantastic content as always. Even as a software engineer with 20+ years experience, I always find something interesting on your channel and plenty of content to refresh things tucked away in my ageing brain 😂 keep up the excellent work! 👍 (one minor criticism for this vid is that I thought face cam was a little large and blocking some of the code changes you were making)
Liskov - The inheriting class should complement, not replace, the behavior of the base class. In our case we should definitely write area calculate logic
I really missed Amigoscode, I can't believe he still can take his time to share these incredible resources and knowledge during this fasting period, thanks Nelson 🙏🙏🙏
► Get NordVPN exclusive deal here: nordvpn.com/amigoscode
Try it risk-free thanks to their money-back guarantee!
► Grab your copy Clean Code copy here: amigoscode.hypg.es/amzn/clean-code
► Git Repo with examples: amigoscode.hypg.es/github/amigoscode/solid
unfortunatly the link to the book is not working (Error 404)
Assalamu aleykum, brother! Ramadan Mubarak 😁
I use these shortcuts quite often, maybe it is useful for you too :)
For mac
Delete line at caret ⌘⌨
Extend selection ⌥↑
Github repo link is not working
Design Patterns would be great
Please make a video for Design patterns, as it will be beneficial for all developers. Thanks for your effort in bringing useful content to the community. Highly appreciated!
Yes, we all need simple explanation about Abstract Factory and Factory Method
@@fuckwdf Helpline📲📥⬆️
Questions can come in⬆️
Helpline📲📥⬆️
Questions can come in⬆️..
@@fuckwdf Have you seen this: th-cam.com/video/ZFwNNsPW3-Q/w-d-xo.html ? Found it really clear.
SOLID is a must know skill in OO development but I think we should be willing to modernise it and make it fit in 2022 when industry is moving towards functional coding. I’m a 20 year c# vet and do full solid on most projects but it’s hard to justify the abstractions for smaller projects. You end up with too many single method classes which can be functions instead.
Why does it matter if you have a single function or a single class with a single method? You're gonna have more files true, but still I dont see a problem here.
@@ivanvelinov4630 Overhead, both In computer and cognitive sence. Besides it is unnatural to put everything into its own box. Generally it is easier to spot a thing put into a bigger box, with many other things, rather than if everything, no matter how small was put into its own box, even if there is a label on each box. It's mentally draining, and the biggest nonsense of OOP to me, besides it is never used on big real life projects. The same with the modern notion of microservices. We are not far away from the time, when a new "breakthrough" in the programming would be ”discovered” in the form of a revolutionary notion for “macroservice“ (highly sarcastic here) as it is functional programming now. Something old, then forgotten in favor of the new hype, and then rediscovered as something “revolutionary" (sarcasm)
And who says grouping "related" functions/methods into a single class (eg. Utility classes) breaks SOLID?
I really missed Amigoscode, I can't believe he still can take his time to share these incredible resources and knowledge during this fasting period, thanks Nelson 🙏🙏🙏
Great video!
About the Liskov Substitution principle, although your explanation was right, the description should be exactly the opposite: every base or parent class should be substitutable by its derived or child classes. So, taking your example, if we have:
Shape shape = new Shape();
shape.area();
in our code, we should be able to substitute the first line for:
Shape shape = new NoShape();
but this would throw an exception, so we don't fullfil this principle.
On the other side, if we have:
Animal animal = new Animal();
animal.eat();
We could substitute it for:
Animal animal = new Dog();
and it would still work as dogs have to eat.
Hope that makes it more clear.
Also, please correct me if I'm wrong, he didn't have to create a new class to demonstrate LSP. The fact that he has a function that accepts "Shape" and it works even when it's supplied with objects of different shapes (Square, Circle, etc), that in itself obeys LSP because all of those are derived from "Shape".
I've been working as a software engineer for 2.5 years and do my best to obey the SOLID, this is by far the best explanation video of all the principles. Usually the interface segregation and liskov were not explained or ignored in case of languages like Ruby ( my first job / 2 years). Kudos man
Masha Allah. As a non-english person, I can clearly get the information. what an amazing explanation 😍
You are a blessing to java developers. We got your back
Best Solid principle tutorial on internet.Crystal clear explanation!!
Hi Amigoscode, thank you for the great video, however one thing to notice: I might be wrong, so feel free to correct me: The single responsibility is not about having a single purpose, but rather about having a single customerbase "single actor/purpose" whom the class/functionset is being programmed for. The functions should not be shared amongst different stakeholders like the finance team and the HR team in a company that both need a way to calculate the salary of a person - they should have different codebases for that because they are different actors. The principle of having a function do only one thing is not part of the Solid Principles of Uncle Bob, even if it is a very wise thing to do. (Read more in "clean architecture" by uncle bob.)
This is probably the fourth or fifth SOLID video I’ve seen since being introduced to the topic and, while they have all been informative, yours sunk in. Thank you so much for this. New Sub!
Would love to see a video on Design Patterns!
This is one of most important topic (and design patterns) that every developer should learn to write better code. I've met experienced developer who didn't know about these subjects and it's so unfortunate. Thanks a lot 💪🏾
I really hope this challen blows up, because this man makes very helpful videos.
Huge respect to people who know Java. It has been kinda hard for me to get into the language but this was extremely helpful!! But once again huge respect to people who can write clean java code while keeping all these in mind, just blows my mind.
Thanks for the video! One small point, I think it will be great vs run app each time, create few tests and run this test to show in own example that you like tests and how it is easy to work with tests.
Thank you for such a clear and concise tutorial. You made a topic that seemed complicated easy to understand. I appreciate it!
I, m reading articles about SOLID principle recently. This video really helps me upderstand how to implement this princople.
Your videos are awesome. Thanks from Taiwan!!
Design patterns with examples will be priceless.
I feel bad with my adblock when the content is excellent like this. I disabled it and rewatched it gain.
Hi Nelson, I'm new here, with no background of Computer Science, and your videos helped me a lot to understand the base of Java, right now I'm following an acreditate course, I would love if you can do videos about Generics, and explain Threads and Stream and Lambda, more understable for a begginer! We really love you! You are a good menthor and teacher! Bless!
I love how this focuses on the Principles
It took me some time to understand Single responsibility. Each class can and should have more than one method, how do you do for them to have only one responsibility. The answer lies in "reason to change" as far as I know. Soo you should ask yourself what would make your code to change, like csv to json or saving in a file or a database or a queue.
Many thanks to you. I'm preparing for a interview and I just forgot all the definition of SOLID principles(event using some of them), and your video helped me a lot to refreshing my memory.
When Nelson writes code, all seems simple. Thanks to share your know with us.
Great lecture. On a minor point, a cube has a volume rather area.
It would be nice if you can provide some videos on Design Patterns
I'm from Argentina and i'm surprise about the quality of your videos, with two videos i learned too much. You're incredible, keep it upppp
Thank you for letting me have a touch on the beauty of the programming.
Hi, I just want to tell you that I love your teaching and I learn from your videos.
The SOLID principles are something I struggled with to abide by early one in my career and struggled walk explaining in interviews. This has definitely helped remember some examples and helped my understanding, cheeers! :D
Thanks bro, that was amazing, good explanation
Hello, sir!
I want to thank you very much, for the tutorials and the work you are doing, and the effort you put in these youtube videos.
Thanks to your tutorials, here in this youtube channel, I managed to land a job as a Java developer.
Never give up guys! Hard work pays off!
Congrats 🍾🎉
Congrats man! Absolutely agree with u!
I'm so glad I found your channel, you're a great teacher. Thanks so much!!
Thank you so much. After a long time not I can clear my understanding of the SOLID principles after watching this video.
Excellent tutorial! This explanations about SOLID principles would have been so precious to have at the begging of my career, I really hope it can help others in their beginning! For me it was excellent for refreshing knowledge!
Best explanation!! If someone needs a refresh on SOLID, this is the Video!
No one could explain these principles better than you, even Uncle Bob! 😄
I have literally just skiped that class in my university, thank you very much for being just in time lol!
wow! this is a great lesson. As a beginner in Java Spring Boot, it gives me an edge to improve and write correct code. thanks Nelson
This was one of the most clear and simple to understand. Thanks
That was the best explanation that I've ever seen about SOLID !!! Thanks
Best description I've seen so far. Thank you.
The last is just waaw and it's used in the most framework especially in Spring framework, thank you so much, this will help me a lot to become a better developer 😎
It's simple and clear, as it should be. Thank you
Amazing explanation as always. Can't be explained faster than this. Much appreciated!
I really appreciate this video, simple explanation to a difficult topic.
Thanks dear brother may ALLAH accept your duaa, fasting, and prayers :)
SOLID PRINCIPLES
►IP Single Responsibility
Each class should have only one sole purpose, and not be filled with excessive functionality
►Open Closed
Classes should be open for extension and closed for modification.
In other words, you should not have to rewrite an existing class for implementing new features.
►Liskov Substitution
This means that every subclass or derived class should be substitutable for their base or parent class
►Interface Segregation
Interfaces should not force classes to implement what they can't do.
Large interfaces should be divided into small ones.
►Dependency Inversion
Components should depend on abstractions,
not on concretions.
Great teaching methodology. Best that i have seen about SOLID explanations!
More test tutorials please i've only found two videos which were amazingly beneficial
Even though I code in C#, I can still follow a lot of what you are teaching.
I love your humour and just your upbeat vibe
😊 Ty for the vid, very useful
Fantastic explanation! BEST VIDEO about SOLID
I have been looking for a tutorial on hexagonal architecture, if you can do a video with a complete demo on that it would be great.
Thanks, this cleared me the basics very well.
Thanks for your knowledge, good teaching.
I really appreciate it
Thank you nelson for all these videos
Best explanation of SOLID principles man! Very good job, thank you very much!
Thank you for recommending the book. It has helped me a lot!
Great video, i really appreciate how do you explain things, hugs from Brazil.
Kind suggestions for future videos:
Live stream with interview questions that we try to answer
A video about concepts that every junior developer must know with examples like this video
AleykumSelam Mashallah brother the cleanest explanation that can be found ever! Finally everything is in place on SOLID principles. I appreciate and strongly recommend it.
Much clear, but I have a question that why didn't you make the ThreeDimensionalShape interface inherited from the Shape interface? Is the interface inheritance an unusual practice, or there was another reason?
I thought just like you. However, in my view, he just wanted to make it as much as simple.
So wonderful, thanks a lot Jamal
this is actually very amazing thank you for your clear and concise tutorial
Iam wondering if there is a specific reason why you are using the Object class instead of Generics?
For example in:
public int sum(List shapes) {...} -> why not do this instead:
public class Areacalculator {
public int sum(List shapes){...}
then you wouldnt have to bother about typesafty afterwards. but iam relatively new to OOP so please enlighten me if iam mistaken.
It was a very benefit episode, thanks for the effort
Just worth a mention, the open closed principle here could be addressed with visitor design pattern.
Great video! Very clear SOLID Principles explanation
Thank you! You are always smiling, so nice)))))
Design Patterns in the Spring boot Framework is a must :)
Hey Please make complete detailed video on all types of design patterns. Thanks :)
Thank you so much Nelson. Best explanation 👍👍👍👍👍👍
i was searching for this type of tutorial . u readd my mind bro.
Amazing explanation with clear examples. Thanks so much!
Great video!! I had never really understood the SOLID principles before but this and with the examples explains them really well
Hi amigo can please make videos on java Design structures.
Very useful and easily understandable video. Good job!
Finally an easy explanation... Although still a bit confused on the last one.
And btw can you make a video on design patterns?
Thanks
Really clear explanation! Barakallahufiik
Can you start a series on Data Structures and Algorithms as well as competitive coding?
Next video on design patterns much appreciated
wow.. thanks a lot. this is what i need. will share this with my team
Nice, borther! I am revising deeper lots of fundamental knowledges from your tutorials! May Allah bless your good deeds!
Please make a complete playlist of GOF design patterns with code example?
Exactly the video that I was looking for! Excelent as always!!!
Good video, I abstracted more about this S.O.L.I.D Principles content. Thanks, bro!
Hello, thank you for this well explained reminder. Just a little remark regarding the video format: can you reduce a little bit the size of your camera so we can see the whole code in your screen. Not that i don't want to see you lol but just for confort. Again thank you very much for all your work my friend. Salam.
the amigoscode videos are always the best!!!
Hi! Where is new lecture about design patterns? It will be amazing to learn it with you!
Fantastic content as always. Even as a software engineer with 20+ years experience, I always find something interesting on your channel and plenty of content to refresh things tucked away in my ageing brain 😂 keep up the excellent work! 👍
(one minor criticism for this vid is that I thought face cam was a little large and blocking some of the code changes you were making)
Jazakallah khair Amigos, great knowledge :)
Really helpful. My first video on this channel and I am surprised :)
Liskov - The inheriting class should complement, not replace, the behavior of the base class. In our case we should definitely write area calculate logic
Great Video! Really helped me understand the concepts
That was a SOLID video. Thanks a lot.
Design Patterns pleaaase, will be so helpfull, thansk a lot for sharing
Hey man, you forgot to split the part from ISP and DIP, in the end of the video. Nice video, by the way.
Good job, Thank you for explain solid patterns. Congratulations.
I really missed Amigoscode, I can't believe he still can take his time to share these incredible resources and knowledge during this fasting period, thanks Nelson 🙏🙏🙏
not like you are unable to do anything while fasting
@@uncomputable929 how long does the post last ?
@@uncomputable929 I actually found out that fasting makes me do more stuff, not less