SOLID: Interface Segregation Principle

As your application grows you are tempted to add methods linked to different responsibility to an existing interface. It is better to separate that new method out into its own interface.

SOLID: Liskov Substitution Principle

Most of the time when building systems using OOP, we're looking to use composition over inheritance, however, when the need is there to use inheritance it's advisable that it's done using the LSP. The Goal of this principle is to prevent our old codebase from breaking due when doing inheritance.

SOLID: Open Closed Principle

The Open-Closed Principle (OCP) states that software entities (classes, modules, methods, etc.) should be open for extension, but closed for modification.

SOLID: Dependency Inversion Principle

All programs are composed of functions and data structures and the SOLID principles introduced by Robert C. Martin, help us group our code into modules and advise how to interconnect them.The goal of the SOLID principles is to build software structures like Lego blocks that can be easy to change, understand and swap out.

SOLID: Single Responsibility Principle… simply explained

All programs are composed of functions and data structures and the SOLID principles introduced by Robert C. Martin, help us group our code into modules and advise how to interconnect them.The goal of the SOLID principles is to build software structures like Lego blocks that can be easy to change, understand and swap out.

Clean Architecture: Key Concepts

There are key components to any application structure. Here we cover what these components are. The components allow us to organize our code. The application then becomes easy to maintain and flexible to change.