Dependency Injection (DI) is one of those terms advanced programmers throw out with an expectation and assumption of full understanding on the part of the receiver. People often wonder what is a good DI product and how to use it. It's easy to get infatuated by a cool buzz phrase, especially when you hear so many others using it. But to truly understand something you need to start by understanding the problem spaces that it is trying to solve. To write testable software, you need to understand and embrace abstractions and injecting them. But then you introduce the problem of having to resolve dependency chains. This is where using a DI container helps you solve both these issues. You'll learn how to make your code testable and maintainable with the help of a DI container. If this is something your organization has not fully embraced yet, come and prepare for a tremendous wow factor.
You will learn:
- About demonstrating problem code
- How to embrace abstractions for across-the-board testability
- About using a full-featured DI container