Skip to content

Latest commit

 

History

History
12 lines (7 loc) · 526 Bytes

File metadata and controls

12 lines (7 loc) · 526 Bytes

Dependency Inversion Principle (DIP)


Important This principle advises developers to avoid hard-coding dependencies on lower-level modules directly into higher-level modules, but instead to depend on abstractions (like interfaces or abstract classes). In practice, this often means using techniques such as dependency injection, where dependencies are "injected" into a class from an external source. This leads to more flexible and reusable code.


Examples

Example in C#