Every design pattern solves specific design problems, but any single pattern is not necessarily appropriate for every case that you come across. A pattern or methodology you are applying should be chosen because it is the right choice for the given problem, not just because you know it and wish to implement it.
Dependency injection is a pattern (and not a framework), so you need to consider the right scenario to implement it. There are chances that may make DI become redundant. It is not necessary to inject everything in your code. If you do so, the purpose of making the code decoupled is not achieved properly; instead, the dependency graph becomes ineffectual.
Evidently, DI produces great flexibility in terms of code ...
