Introduction

SOLID principals are basic rules to follow when programming:

Single-responsibility principle -

"There should never be more than one reason for a class to change."

Open–closed principle -

"Software entities should be open for extension, but closed for modification."

Liskov substitution principle -

"Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it."

Interface segregation principle -

"Many client-specific interfaces are better than one general-purpose interface."

Dependency inversion principle -

"Depend upon abstractions, [not] concretions."

SOLID principals can fit inside whole course, in this course the basics will be shown with examples and challenges.

Read more