tal95shah / SOLID_Principles

:fire: :zap: SOLID Design Principles explanation with diagrams, examples in C++. :rocket: Motivation behind each principle is explained. Difference between good code and bad code is defined.

SOLID Design Principles using C++

• Single Responsibility Principle
  

• Interface Segregation Principle
  

• Open Closed Principle
  

• Liskov Substitution Principle
  

• Dependency Inversion Principle
  

What happens if we don't use SOLID?

• Tight coupling occurs
• Duplication of code
• Unknown issues in application development lifecycle
• requires time to do modification in code
• code not testable

---

Why use SOLID?

• reduces complexity of code.
• reusability
• reduces error
• increase readability, extensibility
• better testability
• reduces tight coupling

Solution to successful development of app depends on?

• Architecture (e.g MVC)
• Design Principles (e.g SOLID)
• Design Patterns (e.g Singleton)