title: Does dependency injection increase my risk of doing something foolish?
body: <p>I'm trying to embrace widespread dependency injection/IoC.  As I read more and more about the benefits I can certainly appreciate them, however I am concerned that in some cases that embracing the dependency injection pattern might lead me to create flexibility at the expense of being able to limit risk by encapsulating controls on what the system is capable of doing and what mistakes I or another programmer on the project are capable of making.  I suspect I'm missing something in the pattern that addresses my concerns and am hoping someone can point it out.</p>
  
  <p>Here's a simplified example of what concerns me.  Suppose I have a method NotifyAdmins on a Notification class and that I use this method to distribute very sensitive information to users that have been defined as administrators in the application.  The information might be distributed by fax, email, IM, etc. based on user-defined settings.  This method needs to retrieve a list of administrators.  Historically, I would encapsulate building the set of administrators in the method with a call to an AdminSet class, or a call to a UserSet class that asks for a set of user objects that are administrators, or even via direct call(s) to the database.  Then, I can call the method Notification.NotifyAdmins without fear of accidentally sending sensitive information to non-administrators.</p>
  
  <p>I believe dependency injection calls for me to take an admin list as a parameter (in one form or another).  This does facilitate testing, however, what's to prevent me from making a foolish mistake in calling code and passing in a set of NonAdmins?  If I don't inject the set, I can only accidentally email the wrong people with mistakes in one or two fixed places.  If I do inject the set aren't I exposed to making this mistake everywhere I call the method and inject the set of administrators?  Am I doing something wrong? Are there facilities in the IoC frameworks that allow you to specify these kinds of constraints but still use dependency injection?</p>
  
  <p>Thanks.</p>