► 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)
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!
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
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, 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!!
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 💪🏾
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!
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
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.
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!
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.
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.
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!
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 😎
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.)
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.
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.
Great video, been watching your vids for a while and although I work primarily in C# at work, your videos are very easy to follow and learn from. Keep up the good work! Also great to see more brits doing software eng videos, as UA-cam seems to be awash with Americans talking about software engineering!
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.
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)
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 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: ua-cam.com/video/ZFwNNsPW3-Q/v-deo.html ? Found it really clear.
You are a blessing to java developers. We got your back
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?
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!
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
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 🙏🙏🙏
Would love to see a video on Design Patterns!
Best Solid principle tutorial on internet.Crystal clear explanation!!
Masha Allah. As a non-english person, I can clearly get the information. what an amazing explanation 😍
I really hope this challen blows up, because this man makes very helpful videos.
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, 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!!
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
Hi, I just want to tell you that I love your teaching and I learn from your videos.
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 💪🏾
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 feel bad with my adblock when the content is excellent like this. I disabled it and rewatched it gain.
Thank you for such a clear and concise tutorial. You made a topic that seemed complicated easy to understand. I appreciate it!
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
Best explanation!! If someone needs a refresh on SOLID, this is the Video!
The best tutorial is included with examples. Thank you!
Thanks bro, that was amazing, good explanation
Best description I've seen so far. Thank you.
That was the best explanation that I've ever seen about SOLID !!! Thanks
Thank you so much. After a long time not I can clear my understanding of the SOLID principles after watching this video.
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.
I'm so glad I found your channel, you're a great teacher. Thanks so much!!
Design patterns with examples will be priceless.
Amazing explanation as always. Can't be explained faster than this. Much appreciated!
Fantastic explanation! BEST VIDEO about SOLID
I love your humour and just your upbeat vibe
😊 Ty for the vid, very useful
Thank you for letting me have a touch on the beauty of the programming.
Great teaching methodology. Best that i have seen about SOLID explanations!
When Nelson writes code, all seems simple. Thanks to share your know with us.
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!
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 have literally just skiped that class in my university, thank you very much for being just in time lol!
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.
I love how this focuses on the Principles
Exactly the video that I was looking for! Excelent as always!!!
It would be nice if you can provide some videos on Design Patterns
i was searching for this type of tutorial . u readd my mind bro.
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!
Great lecture. On a minor point, a cube has a volume rather area.
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 😎
No one could explain these principles better than you, even Uncle Bob! 😄
Best explanation of SOLID principles man! Very good job, thank you very much!
This was one of the most clear and simple to understand. Thanks
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.)
Great video, i really appreciate how do you explain things, hugs from Brazil.
Great video! Very clear SOLID Principles explanation
It was a very benefit episode, thanks for the effort
Thank you nelson for all these videos
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
Thank you so much Nelson. Best explanation 👍👍👍👍👍👍
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.
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.
Thanks, this cleared me the basics very well.
the amigoscode videos are always the best!!!
I really appreciate this video, simple explanation to a difficult topic.
So wonderful, thanks a lot Jamal
Thanks for your knowledge, good teaching.
I really appreciate it
It's simple and clear, as it should be. Thank you
Dude another quality video. Thank you.
Ma sha Allah 👍 Very good video.
Eid mubarak.
Jazakallah khair Amigos, great knowledge :)
Very useful and easily understandable video. Good job!
Thank you! You are always smiling, so nice)))))
It was very informative! Thank you Amigoscode! :)
Good video, I abstracted more about this S.O.L.I.D Principles content. Thanks, bro!
Great Video! Really helped me understand the concepts
this is actually very amazing thank you for your clear and concise tutorial
Thank you for recommending the book. It has helped me a lot!
Great video, been watching your vids for a while and although I work primarily in C# at work, your videos are very easy to follow and learn from. Keep up the good work! Also great to see more brits doing software eng videos, as UA-cam seems to be awash with Americans talking about software engineering!
Amazing explanation with clear examples. Thanks so much!
You´re amazing, bro!! Thanks a lot for spending your time to share your knowledge!!!
wow.. thanks a lot. this is what i need. will share this with my team
Great video!! I had never really understood the SOLID principles before but this and with the examples explains them really well
As always, top class stuff.
Bro you're the best
Thanks a lot 💙
Always you are the best.
Nice, borther! I am revising deeper lots of fundamental knowledges from your tutorials! May Allah bless your good deeds!
You really deserve a lot more subscribers!
Nice work bro 👌🖐️🇺🇦
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.
Really helpful. My first video on this channel and I am surprised :)
More test tutorials please i've only found two videos which were amazingly beneficial
Really clear explanation! Barakallahufiik
Love this video!
Very good and easy explanation!
Even though I code in C#, I can still follow a lot of what you are teaching.
That was a SOLID video. Thanks a lot.
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)
Much love bro! I needed this
Salam Alaikum. I was just thinking of you earlier today. Really miss your videos. Keep up the good work
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.
Design Patterns in the Spring boot Framework is a must :)
Assalamu Aleykum Amigo) thank you for this really simple explanation of SOLID principle!
Next video on design patterns much appreciated
It was really easy and fun! Thanks Nelson!
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