SOLID Design Principles
SOLID is an acronym for 5 design principles related with Object-Oriented Programming (OOP). When correctly applied SOLID principles make software more maintainable, flexible and understandable. SOLID represent a subset of multiple principles proposed by Robert C. Martin in the 90s.
Here is a serie of articles each covering a SOLID topic:
- The Single Responsibility Principle (SRP): Guidelines to partion your logic into classes
- The Open-Close Principle (OCP): Modules should be open for extension and closed for modification.
- The Liskov Substitution Principle (LSP): Methods that use references to base classes must be able to use objects of derived classes without knowing it.
- The Interface Segregation Principle (ISP): Client should not be forced to depend on methods it does not use.
- The Dependency Inversion Principle (DIP): Depend on abstractions, not on implementations.
SOLID principles help guiding the usage of powerful concepts of Object Oriented Programming (OOP). But they are subjectives. Hence SOLID principles are subject to debate and opinion.
Here is a serie of articles that explain how SOLID principles can be used in the real world: