SOLID: Dependency Inversion Principle (DIP)

Hi! This is the final article about SOLID principles, I hope it was nice for you to dip (ba-dum-tss) in these! As said before, learning is probably the main point of being a good developer. Some guys recommend to learn one language per year, other developers tend to debate about sticking to one single language or not, but as long as you learn something new every day, you're making yourself a better developer every day.

"D" for DIP

The Dependency Inversion principle tells you to make sure that your classes should depend on the most abstract implementation of what you need. This is important to make them the most flexible possible, and it's specificly true for open-source projects that must be extensible and flexible! SOLID: Dependency Inversion PrincipleThe Dependency Inversion principle tells you to make sure that your classes should depend on the most abstract implementation of what you need. This is important to make them the most flexible possible, and it's specificly true for open-source projects that must be extensible and flexible! SOLID: Dependency Inversion PrincipleThe Dependency Inversion principle tells you to make sure that your classes should depend on the most abstract implementation of what you need. This is important to make them the most flexible possible, and it's specificly true for open-source projects that must be extensible and flexible! SOLID: Dependency Inversion PrincipleThe Dependency Inversion principle tells you to make sure that your classes should depend on the most abstract implementation of what you need. This is important to make them the most flexible possible, and it's specificly true for open-source projects that must be extensible and flexible! SOLID: Dependency Inversion Principle

All the SOLID articles on KNPLabs:

• Single Responsibility Principle
• Open/Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• » Dependency Inversion Principle