Can you list the main principles embedded in SOLID for developing resilient and extendable programs?

SOLID is a set of five principles of object-oriented programming that help create resilient, extendable, and maintainable code:

• S (Single Responsibility Principle) — The single responsibility principle: a class should have only one reason to change, meaning it should perform only one task.

• O (Open/Closed Principle) — The open/closed principle: software entities should be open for extension but closed for modification.

• L (Liskov Substitution Principle) — The Liskov substitution principle: objects of subclasses should be interchangeable with objects of the superclass without affecting the correctness of the program.

• I (Interface Segregation Principle) — The interface segregation principle: it is better to have several specific interfaces than one general-purpose interface.

• D (Dependency Inversion Principle) — The dependency inversion principle: high-level modules should not depend on low-level modules; both should depend on abstractions.

These principles help write code that is easier to test, extend, and maintain.