I'm relatively unskilled in Dependency Injection, and I'd like to learn some best practices and anti-patterns to use and avoid respectively when using DI.
I really enjoyed this article regarding DI, as it's targeted towards people who don't have a ton of DI experience, or don't even know what it is.
https://mtaulty.com/2009/08/10/m_11554/
What’s Unity?
It’s a “dependency injection container”.
Now, at that point a bunch of folks reading this will say “Yes, we know and we’re already using it for reasons A, B, C or we’ve elected not to use it for reasons X,Y,Z ” and I imagine a bunch of other folks might say;
“Huh? What’s a dependency injection container?”
This post is for the latter people – it’s not meant to be exhaustive but hopefully it’s not completely unhelpful either :-)