Learning Single Responsibility Principle
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.
Unlock now
Introduction to SOLID Principles
Robert C. Martin introduced the SOLID principles of object-oriented programming in 2000. SOLID is an acronym for:
Single Responsibility Principle
This principle states that a class should have only one responsibility and, consequently, only one reason to change. For example, if you have a Book class that needs to be updated because you’re updating a Pencil class, then you’re not following this rule.
Advantages of the Single Responsibility Principle
This principle helps to write minimal, focused tests for each class, promotes decoupling, organizes code better, and makes code more readable and understandable. It becomes easy to tell where to find functionality and what a class does.