What are solid principles explain with example and also tell where you used them in previous project

Question

Accepted Answer

Solid principles are a set of design principles for writing maintainable and scalable code.

Single Responsibility Principle: A class should have only one reason to change. For example, a class that handles user authentication should not also be responsible for sending emails.
Open/Closed Principle: Software entities should be open for extension but closed for modification. For example, using interfaces to allow for new implementations without modifying existing code.
Liskov Substitution Principle: Objects of a superclass should be replaceable with objects of its subclasses without affecting the correctness of the program. For example, a square should be able to substitute a rectangle.
Interface Segregation Principle: Clients should not be forced to depend on interfaces they do not use. For example, breaking down large interfaces into smaller, more specific ones.
Dependency Inversion Principle: High-level modules should not depend on low-level modules. Both should depend on abstractions. For example, using dependency injection to decouple classes.

Popular interview questions of Senior Executive