← Glossary
What does "single responsibility" mean in programming?
single responsibility is one of the most common terms in software development. This guide explains what it means, how it is used in practice, and why it matters, with real examples from the developer world.
Definition
A design principle stating that a class or module should have one, and only one, reason to change. Part of the SOLID principles. Keeps modules focused, easier to test, and less likely to break when adjacent features change.
Example
"This class sends emails AND validates addresses — split it. Single responsibility: one job per class."
Related terms
Ready to practice your English at work?
Lingua-e has interactive exercises built around real developer conversations: standups, code reviews, retrospectives, and more. Practice until it comes naturally.
Try Lingua-e for free