The solid principles as one liners

SOLID is an acronym which stands for Single responsibility principle – every software entity (object, module etc) should have only a single responsibility and one reason to change. Open/closed principle – every software entity should be open for extension, but closed for modification. Liskov substitution principle – closely related to design by contract and it […]

The single responsibility principle

”A class should have one, and only one, reason to change.” – Robert C Martin If I had to choose one design principle that has been most useful to practice over time it surely is the single responsibility principle (SRP). What is this principle about? The idea is that a module (or class) should only […]