What does "Interface Segregation Principle" mean in programming?
Interface Segregation Principle 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
The I in SOLID. Clients should not be forced to depend on interfaces they do not use. Split large interfaces into smaller, more specific ones so that implementing classes only need to know about the methods relevant to them.
Example
"We split the fat UserRepository interface into ReadableRepository and WritableRepository so read-only services do not have to implement write methods."
Can you put this sentence in the right order?
Keep building your technical English
You just looked up what this word means. Lingua-e turns vocabulary like this into full practice: fill-in-the-blanks, listening, and real developer conversations.
Practice this for free