---
title: "What are the SOLID principles, explained simply?"  
description: "What are the SOLID principles, explained simply?"  
author: "Mikko Lehtonen"  
published: 2026-11-20  
updated: 2026-11-20  
canonical: https://www.mindstick.com/forum/163090/what-are-the-solid-principles-explained-simply  
category: "software engineering"  
tags: ["SOLID principles", "object-oriented design", "clean code", "Software Architecture", "c#"]  
reading_time: 1 minute  

---

# What are the SOLID principles, explained simply?

I can recite the names of SOLID, but I cannot explain them in plain language or apply them. Help?

## Replies

### Reply by Aman Mathur

- **S, Single Responsibility**: a class should have one reason to change. A class that validates, saves to the database and sends email does three jobs. Split it.
- **O, Open/Closed**: add new behaviour by adding new code, not by editing tested code. For example, add a new `IDiscount` implementation instead of growing a long if/else.
- **L, Liskov Substitution**: a subclass should work wherever its parent is expected, without surprises. If `Square` extends `Rectangle` but breaks width and height rules, it violates this.
- **I, Interface Segregation**: prefer small, focused interfaces. Do not force a class to implement methods it does not use.
- **D, Dependency Inversion**: depend on abstractions, not concrete classes. A service should take an `IEmailSender`, not create a `SmtpEmailSender` itself. That is what dependency injection is for.

These are guidelines, not laws. Use them to reduce pain, such as code that is hard to change or test. Over-applying them to tiny programs creates needless complexity.


---

Original Source: https://www.mindstick.com/forum/163090/what-are-the-solid-principles-explained-simply

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
