Revisions

_posts/06-03-01-Complex-Problem.md

@@ -5,7 +5,12 @@ isChild: true
 ## Complex Problem {#complex_problem_title}
 
 If you have ever read about Dependency Injection then you have probably seen the terms *"Inversion of Control"* or *"Dependency Inversion Principle"*. 
-These are the complex problems that Dependency Injection solves, or to be more precise, elegantly solves.
+These are the complex problems that Dependency Injection solves.
+
+### Inversion of Control
+
+Inversion of Control is as it says, "inverting the control" of a system by keeping organisational control entirely separate from our objects. 
+In terms of Dependency Injection, this means loosening our dependencies by controlling and instantiating them elsewhere in the system.
 
 For years, PHP frameworks have been achieving Inversion of Control, however, the question became, which part of control 
 are you inverting, and where to? For example, MVC frameworks would generally provide a super object or base controller that other 
@@ -15,6 +20,8 @@ dependencies, this method simply moved them.
 Dependency Injection allows us to more elegantly solve this problem by only injecting the dependencies we need, when we need them, 
 without the need for any hard coded dependencies at all.
 
+### Dependency Inversion Principle
+
 Dependency Inversion Principle is the "D" in the S.O.L.I.D set of object oriented design principles that states one should 
 *"Depend on Abstractions. Do not depend on concretions."*. Put simply, this means our dependencies should be interfaces/contracts or abstract 
 classes rather than concrete implementations. We can easily refactor the above example to follow this principle.