title: Dependency Injection Frameworks: Why do I care?
body: <p>I was reading over <a href="https://github.com/ninject/ninject/wiki/Dependency-Injection-By-Hand" rel="noreferrer">Injection by Hand</a> and <a href="https://github.com/ninject/ninject/wiki/Dependency-Injection-With-Ninject" rel="noreferrer">Ninjection</a> (as well as <a href="https://github.com/ninject/ninject/wiki/Why-Use-Ninject%3F" rel="noreferrer">Why use Ninject</a> ).  I encountered two pieces of confusion:</p>
  
  <ol>
  <li><p>The inject by hand technique I am already familiar with, but I am not familiar with Ninjection, and thus am not sure how the complete program would work.  Perhaps it would help to provide a complete program rather than, as is done on that page, showing a program broken up into pieces</p></li>
  <li><p>I still don't really get how this makes things easier.  I think I'm missing something important.  I can kind of see how an injection framework would be helpful if you were creating a group of injections and then switching between two large groups all at once (this is useful for mocking, among other things), but I think there is more to it than that.  But I'm not sure what.  Or maybe I just need more examples of why this is exciting to drive home the point.</p></li>
  </ol>