Robert C. Martin’s definition has two parts:
“A. High-level modules should not depend on low-level modules. Both should depend on abstractions.”
“B. Abstractions should not depend on details. Details should depend on abstractions.”
That sounds academic until you see what it actually means.
Latest Posts
Dependency Inversion Principle: Your Business Logic Should Never Know About Infrastructure