SOLID — Single-responsibility, Open-closed, Liskov, Interface-segregation, Dependency-inversion
Definition: Five object-oriented design principles that make code easier to extend and harder to break. SOLID is the grammar of professional codebases — not a recipe, but a shared vocabulary.
Example
In engineering planning, you'll often hear something like: "Let's pull the latest SOLID numbers before we make a call" — shorthand for single-responsibility, open-closed, liskov, interface-segregation, dependency-inversion.
When you'll hear it
SOLID shows up most often in engineering planning, architecture reviews, and sprint retrospectives. When someone uses it, they're usually referring to single-responsibility, open-closed, liskov, interface-segregation, dependency-inversion — and they expect the room to already know what that means.
FAQs
What does SOLID stand for?
SOLID stands for Single-responsibility, Open-closed, Liskov, Interface-segregation, Dependency-inversion.
What does SOLID mean in technology and engineering?
Five object-oriented design principles that make code easier to extend and harder to break. SOLID is the grammar of professional codebases — not a recipe, but a shared vocabulary.
Where will I hear SOLID used at work?
SOLID comes up most often in engineering planning, architecture reviews, and sprint retrospectives. It's used as shorthand for single-responsibility, open-closed, liskov, interface-segregation, dependency-inversion, so people assume you already know the term.