If you like this video and want to learn C# in depth from me, visit www.skillfoundry.io! The learning pathway takes you from zero to professional-level coding skills, but be prepared for rigor and depth. It takes over 700 hours to complete, with 80+ exercises and 12+ substantial capstone projects.
If anyone is curious why it's called dependency inversion, it is because instead of the class depending on lower level details (where the choices come from), it now depends on a HIGHER level abstraction (the interface), thus the dependencies were inverted
Hi! I'm the creator of the kangaru dependency injection library for C++. What I love about that tutorial is that you teach beginners to do it without a framework. A dependency injection library is only there to automate boilerplate that happens in the wiring code, and not essential for dependency injection. Another point (for more advanced programmers) is that technically, dependency injection don't require interfaces to work. union (sum types) or enums can also do the trick when you want your component to let users choose its behaviour, but have a closed set of possible behaviour. This still enable testing without introducing virtual function calls when unneeded. In my case, which might be a C++ only thing, adding virtual functions (any overridable function) strictly only for the purpose of testing is smelly code. I try to keep behaviour choices as closed as possible and thus do my DI with concrete types when possible with the choice of behaviour being values inside those concrete types.
@@SkillFoundryIO Yeah, but definitely something that will only appear with larger projects, or projects with tight performance requirements. Out of the scope of the video, but still worth mentioning here in the comments :)
Thank you for the concrete example to make sense of the topic. Most of the other videos I've found implement a very generic Class1 with interfaceA or whatever but seeing an actual working application and how the changes are done finally made it click for me.
It’s both the hardest and most rewarding part of teaching- finding examples that are real enough but not overly complicated. Thank you for the kind words!
I will say you are the great master teacher. You have extra ordinary skills and techniques for teaching lots of blessing from all who watched this videos.
I’m learning programming as a hobbyist and to make my work life easier. I am at the stage where I have learnt the basic C# syntax and solving individual problems. Now trying to start learning OOP, this is a really helpful approach to start understanding it’s uses!
What an amazing explanation for a very confusing topic to beginners like myself, you even added the testing example that so many people mention but never show! Great work, will definitely follow your channel for more content.
Fantastic explanation and example for DI!! You teach both the concept of DI as well as how it is implemented in c#. Simple and to the point. Great job.
I'd been lookin for good interface explanation until I found your channel. And you did best of what you could. Explained interfaces and DI at once, on working example. Fantastic job! Great content, great teaching approach, wide perspective filled with necessary details without overhelming the learner and topic. All the best for you and your channel!
You are so humble and awesome in your explanations! I dont yet grasp it as iam farely new, but I did have exactly these beginner issues of too much coupling, will learn & apply dependency injection in the future!
I’ve noticed a lot of tutorials show how but don’t spend much if any time on the why. It’s one of the reasons in our courses we refactor projects as we learn new techniques so our learners can better see the difference between novice and professional approaches!
I have to say that every time I read something about dependency injection, I kinda understand a bit of it yet still feel that it's an intimidating concept. But your explanation is so cool and simple. Thank you for making this. I love the example and really want to try it out right now.
Great job explaining! First time, after watching many related videos, I could follow the explanation and got it. Presented at the right pace with good examples. Thank you!
Sorry, I haven't set up a GitHub repository for the UA-cam channel. Honestly didn't think about it. I'll put that on my list of things to do this month.
Sir, this was OUTSTANDING! Thank you so much! I really appreciated you talking slowly thru it. Really helped me not to too confused along the way. You make a great teacher!
Thank you for the video! This is one of the best explanations for Dependency Injection. And one of the best demonstrations of the right approach to programming.
This was some incredible explanation! I was realy struggleing with the concept at first but now after the video how I even struggled at the first place! Great video!
Thanks for this video. Seems strange to have the actual console, the view, inside of an interface class? Does that restrict how the human player is implemented? What if you were moving this to a WPF app?
Love the short but rly clearly overview and example, of what dependency injection is. At the begin i thought it was some evil stuff, but learned fast, its simple and rly helpful.
Hi this is great, am at 0:53 and see its a BLACK SCREEN with faint letters in tiny font? I started computers in the 70s, the monitors had extreme contrast by todays standard. This is eye strain, any way you can do one episode with the "normal" white background and dark blue text thats zoomed so it looks 18pt or so? why, WHY??? do people feel the need to use the black background? why? I have alot to say about DI and making changes to it. Thank you
Can you do a video on the concept of "Clean Code". Also utilizing abstract classes and interfaces to achieve clean code. I've been interviewing a lot lately and Object Oriented Design style interviews have been creeping up a lot (Amazon famous for it). I personally would love it if you did.
I have been searching for weeks and watching tens of videos on the subject. I finally found it on your channel. Thank you for sharing 😂. It's clear to me now. I'm subscribing to your channel 😊.
This is exactly the approach we took in our project. OOP in C# is not complete if not done with DI. Dependency Injection was intimidating at first but once you fully understood its principles, you'll get addicted to using it in your OOP implementation.
Agreed! There is always a trade-off for complexity, so for really simple things like batch jobs I sometimes skip it, but for the most part you should be implementing it, especially between layers of your project.
Thank you sir you’ve saved me ❤️ you way of explaining the concept is really amazing and the example itself is simple. Please explain the dependency injection container too 🙏 thanks again
A clear explanation. I sometimes struggle to get across to people how simple this concept is. BTW, having constant 1980s porno music in the background can make videos very difficult to follow for people with a hearing impairment.
Great video. My only recommendation is to maybe forgo the background music. I personally found it a little distracting while trying to concentrate on your voice at times.
Why is this an interface? Why not a class Player that has a choice and then the 2 classes human and computer derive from player? I mean why an interface? It sounds more logic to me to be a class. I’m genuinely asking
There’s a few reasons. What you suggest is polymorphic so you could substitute. However inheritance is an is-a relationship while choosing a type is a can-do. It is more modular and testable to be an interface implementation.
Very good video. Just... I'm not fan of the Iplayer nomenclature... the client of the API you defined does not care if it is interacting with an interface or an implementation. You manager talks to a Player, not to an IPlayer. Same way you interact with a List, not an Ilist, that you can new ArrayList, but the list is not an IList, and the ArrayList is not a ListImpl (I am not fan of the PlayerImpl either). You have a public interface Player, and a public class HumanGamer implements Player, and a BipBoopRandomGambler implements Player...
So this looked to be a pretty good video, but then the background music started up. No added benefit, super distracting. So my recommendation would be to leave it out.
I can never thank you enough! God, It's a gem! The example, the explanation, the accent, the pace.... it's perfect! damn! 🤌🤌 One other thing. The background sound-track is so soothing! What's the track name?
If you like this video and want to learn C# in depth from me, visit www.skillfoundry.io! The learning pathway takes you from zero to professional-level coding skills, but be prepared for rigor and depth. It takes over 700 hours to complete, with 80+ exercises and 12+ substantial capstone projects.
That was the easiest most clear explanation i found so far, thank you so much!
You are very welcome!
If anyone is curious why it's called dependency inversion, it is because instead of the class depending on lower level details (where the choices come from), it now depends on a HIGHER level abstraction (the interface), thus the dependencies were inverted
Absolutely! I left that term off the video because most novices only hear about the injection part. 😇
Thanks for adding more information!
Hi! I'm the creator of the kangaru dependency injection library for C++. What I love about that tutorial is that you teach beginners to do it without a framework. A dependency injection library is only there to automate boilerplate that happens in the wiring code, and not essential for dependency injection.
Another point (for more advanced programmers) is that technically, dependency injection don't require interfaces to work. union (sum types) or enums can also do the trick when you want your component to let users choose its behaviour, but have a closed set of possible behaviour. This still enable testing without introducing virtual function calls when unneeded.
In my case, which might be a C++ only thing, adding virtual functions (any overridable function) strictly only for the purpose of testing is smelly code. I try to keep behaviour choices as closed as possible and thus do my DI with concrete types when possible with the choice of behaviour being values inside those concrete types.
Thank you for your kind words!
I agree on the virtual methods as well, it’s a smelly pattern.
@@SkillFoundryIO Yeah, but definitely something that will only appear with larger projects, or projects with tight performance requirements. Out of the scope of the video, but still worth mentioning here in the comments :)
Eric you are an AMAZING teacher!
Sincerely, a former teacher turned programmer :)
Thank you!
Thanks. You explain DI so clear and simple that even non programmer can understand.
absolutely! I just explained it to my grandma (83 years old, can barely write) and she totally got it.
I am sold when you said "We teach people how to code the right way."
Especially in the current market it’s important to have strong foundations!
This had to be the most clear explanation of dependency injection I've found
Thanks! I iterated a lot back in my Bootcamp days on how to demonstrate it with minimal code.
Thank you for the concrete example to make sense of the topic. Most of the other videos I've found implement a very generic Class1 with interfaceA or whatever but seeing an actual working application and how the changes are done finally made it click for me.
It’s both the hardest and most rewarding part of teaching- finding examples that are real enough but not overly complicated.
Thank you for the kind words!
I will say you are the great master teacher. You have extra ordinary skills and techniques for teaching lots of blessing from all who watched this videos.
Thank you!
As soon as I opened the video and saw your face sir, I felt overwhelmed by a sense of trust. I immediately subscribed.
I’m learning programming as a hobbyist and to make my work life easier. I am at the stage where I have learnt the basic C# syntax and solving individual problems. Now trying to start learning OOP, this is a really helpful approach to start understanding it’s uses!
Stay motivated! OOP is the hardest part, once you get it the rest is not nearly as difficult to learn.
saw this in a Job Description and Now seeing it on UA-cam all in less than 2 hours, The gods wanted me to learn this
Hope it helped! If you want to go deeper into it in C#, check out our main site.
What an amazing explanation for a very confusing topic to beginners like myself, you even added the testing example that so many people mention but never show! Great work, will definitely follow your channel for more content.
Thank you for your kind words!
Fantastic explanation and example for DI!! You teach both the concept of DI as well as how it is implemented in c#. Simple and to the point. Great job.
Thank you for your kind words!
I liked the explanation and example. It would also be helpful to have a link to the before and after source code.
I'd been lookin for good interface explanation until I found your channel. And you did best of what you could. Explained interfaces and DI at once, on working example. Fantastic job! Great content, great teaching approach, wide perspective filled with necessary details without overhelming the learner and topic. All the best for you and your channel!
Thank you!
You are so humble and awesome in your explanations!
I dont yet grasp it as iam farely new, but I did have exactly these beginner issues of too much coupling, will learn & apply dependency injection in the future!
i like the way you teach, explaining things with not too fast speed and i like your energy. you're a great teacher. and I subscribed
Thank you!
You have the perfect pace for teaching.
Thank you!
YOU ARE AWESOME! I was struggling for days trying to understand what is dependency injection, Now I get it!! Thank you with all my heart!
I appreciate the kind words!
Wow, really cool. I've been doing it a lot in my code, but didn't have a complete understanding of how powerful it is
I’ve noticed a lot of tutorials show how but don’t spend much if any time on the why.
It’s one of the reasons in our courses we refactor projects as we learn new techniques so our learners can better see the difference between novice and professional approaches!
I have to say that every time I read something about dependency injection, I kinda understand a bit of it yet still feel that it's an intimidating concept. But your explanation is so cool and simple. Thank you for making this. I love the example and really want to try it out right now.
Awesome! Good luck in your learning!
Great job explaining! First time, after watching many related videos, I could follow the explanation and got it. Presented at the right pace with good examples. Thank you!
You are welcome!
This is an awesome video! The way you explain this concept so clearly and calmly really made me understand it. Thanks!
You are welcome! Now reinforce it with practice!
This video was a great refresher especially after being away from it for so many years! Is there any available code so I can save?
Sorry, I haven't set up a GitHub repository for the UA-cam channel. Honestly didn't think about it. I'll put that on my list of things to do this month.
Sir, this was OUTSTANDING! Thank you so much! I really appreciated you talking slowly thru it. Really helped me not to too confused along the way. You make a great teacher!
Glad it helped!
Thank you, this is so clear and easy to understand.
You are welcome
Thank you for the video! This is one of the best explanations for Dependency Injection. And one of the best demonstrations of the right approach to programming.
Glad it was helpful!
Great explanation! I've been struggling with this concept
Excellent explanation!
one of the best video of this topic. Thank you so much!
Thank you for the clear explanaition
Thanks for watching!
This was some incredible explanation!
I was realy struggleing with the concept at first but now after the video how I even struggled at the first place!
Great video!
Everyone struggles at first my friend
Bro, you are such a good teacher. Thank you so much. You made this concept so understandable.
Thank you!
This video is gold.
Hey, this is the best explanation and examples. Thank you so much!
You are welcome!
GREAT example, thanks for sharing it!
You are welcome!
This video got recommended to me just now. Amazing concept explained flawlessly. Thank you!!!!!!!😊
So clear, first time I understand how usefulin dependency injection.
Thank you!
Beautiful! Thank you!
You are welcome!
really nicely done...any chance you could do a DI container video?
Really helpful video for begginners thank u
You are welcome!
Thanks for this video. Seems strange to have the actual console, the view, inside of an interface class? Does that restrict how the human player is implemented? What if you were moving this to a WPF app?
Yes I was just demonstrating DI. I think going full separation of concerns would be
distracting to the learner.
Love the short but rly clearly overview and example, of what dependency injection is. At the begin i thought it was some evil stuff, but learned fast, its simple and rly helpful.
Perfect explanation, thanks!
Glad it was helpful!
In depth Explanation from a master! Awesome!
Hi this is great, am at 0:53 and see its a BLACK SCREEN with faint letters in tiny font? I started computers in the 70s, the monitors had extreme contrast by todays standard. This is eye strain, any way you can do one episode with the "normal" white background and dark blue text thats zoomed so it looks 18pt or so? why, WHY??? do people feel the need to use the black background? why? I have alot to say about DI and making changes to it. Thank you
If I use the white background people complain too. Sigh…
But done, next video will be default color scheme!
@@SkillFoundryIO Thanks! Im in a very well lit room and have used the white screen since the late 80s when it was possible.
I'll tell you why, developers are vampire these days.
awesome awesome awesome. just brilliant explanation and example
Can you do a video on the concept of "Clean Code". Also utilizing abstract classes and interfaces to achieve clean code.
I've been interviewing a lot lately and Object Oriented Design style interviews have been creeping up a lot (Amazon famous for it). I personally would love it if you did.
I have an SRP video as well, but I haven't had time to get to the rest yet. It'll happen someday.
Absolutely clear!
Best explanation so far. So glad I found your video. Thanks
Great tutorial, its definitely the first one I saw, which does not use any "magic" of a DI container, which is very confusing for beginners.
Very well explained. Great job, thank you 👍
Thank you for your kind words!
Great video! You really good at explaining stuff, well done! Impressive. Keep up the good work!!
Thank you for your kind words!
Nicely explained
Thank you!
Cool,Sir.
I appreciate it .
this was amazon explanation, I love it, thank you
You are welcome!
I have been searching for weeks and watching tens of videos on the subject. I finally found it on your channel. Thank you for sharing 😂. It's clear to me now. I'm subscribing to your channel 😊.
Glad it was helpful!
NIce tutorial! Thanks a lot! Promising channel.
Thank you for the kind words!
The best explanation for this topic!
This is exactly the approach we took in our project. OOP in C# is not complete if not done with DI. Dependency Injection was intimidating at first but once you fully understood its principles, you'll get addicted to using it in your OOP implementation.
Agreed! There is always a trade-off for complexity, so for really simple things like batch jobs I sometimes skip it, but for the most part you should be implementing it, especially between layers of your project.
fantastic video, beautifuly explained and an easy to follow and recode example. Thank you!
Thank you!
Thank you sir you’ve saved me ❤️ you way of explaining the concept is really amazing and the example itself is simple. Please explain the dependency injection container too 🙏 thanks again
You are welcome!
Nice work, with a well chosen example
You are fantastic, thank you.
Thank you! Happy coding!
Thank you so much for this amazing example!
You're very welcome!
Nice explanation keep it up❤
Thanks 🙂
A clear explanation. I sometimes struggle to get across to people how simple this concept is. BTW, having constant 1980s porno music in the background can make videos very difficult to follow for people with a hearing impairment.
Yeah, I told my editor to not have background music in tutorials anymore.
This is an excellent video!
clean code, and maintenance
That's helpful, thank you
2 questions. are you in your bath tub? and does this work the same if I want to use dependency injection in xamarin forms or MAUI?
1. I’ve been upgrading my gear. Didn’t want to over invest if the channel didn’t take off.
2. Yes it works the same.
Gold content!
Another great video! Keep it up! 😄👍
Thanks! Will do!
Thank you! Found something new :)
You are welcome
Amazing video 👌👌
Good content!
Great video
Great video. My only recommendation is to maybe forgo the background music. I personally found it a little distracting while trying to concentrate on your voice at times.
Good feedback, thank you!
Why is this an interface? Why not a class Player that has a choice and then the 2 classes human and computer derive from player? I mean why an interface? It sounds more logic to me to be a class. I’m genuinely asking
There’s a few reasons. What you suggest is polymorphic so you could substitute. However inheritance is an is-a relationship while choosing a type is a can-do.
It is more modular and testable to be an interface implementation.
@@SkillFoundryIO yes and thank you. I was just wondering if you could use the same injection pattern but using inheritance instead of interfaces
you are awesome
made me smile
Very good video. Just... I'm not fan of the Iplayer nomenclature... the client of the API you defined does not care if it is interacting with an interface or an implementation. You manager talks to a Player, not to an IPlayer. Same way you interact with a List, not an Ilist, that you can new ArrayList, but the list is not an IList, and the ArrayList is not a ListImpl (I am not fan of the PlayerImpl either).
You have a public interface Player, and a public class HumanGamer implements Player, and a BipBoopRandomGambler implements Player...
That’s mostly a c# thing. Most devs use the I prefix.
watching in 1.5x speed.. better..
2x
Can you position your camera smaller in the next video? It's a bit distracting.
Absolutely
@@SkillFoundryIO thank you for your reply but its was just irony :)
lol. a switch statement anyone?
So this looked to be a pretty good video, but then the background music started up. No added benefit, super distracting. So my recommendation would be to leave it out.
Thank you. I plan on doing future demos without music.
Lmao. Zero problems with the music. A flawless video, but someone is always going to complain.
I can never thank you enough! God, It's a gem! The example, the explanation, the accent, the pace.... it's perfect! damn! 🤌🤌
One other thing. The background sound-track is so soothing! What's the track name?
Not sure on the music, my editor uses epidemic sound subscription. They have a lot of music like that.