Can you explain the main principles underlying SOLID and their role in software development?

SOLID principles are a set of five fundamental object-oriented design rules that help create flexible, extendable, and maintainable software systems:

1. S (Single Responsibility Principle) — The Single Responsibility Principle: a class should have only one reason to change, meaning it should be responsible for a single task.

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

3. L (Liskov Substitution Principle) — The Liskov Substitution Principle: objects of a subclass should be interchangeable with objects of the superclass without affecting the correctness of the program.

4. I (Interface Segregation Principle) — The Interface Segregation Principle: it is better to have several specific interfaces than a single universal one.

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

Applying these principles helps reduce code coupling, increase reusability, and simplify maintenance.