The Single Responsibility Principle has nothing to do with "do just one thing" - that is a common misconception. The Single Responsibility Principle:
Gather together those things that change for the same reason, and separate those things that change for different reasons.
So "those (many) things that change for the same reason" revolve around the same single responsibility.
Don't Repeat Yourself is another one - it' not about removing repetition or duplication:
Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.
Sometimes duplication isn't about the same thing (The Wrong Abstraction):
prefer duplication over the wrong abstraction
Also: The SOLID Design Principles Deconstructed (2013)
Basics of the Unix Philosophy:
(i) Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new features. (Doug McIlroy 1978)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The Single Responsibility Principle has nothing to do with "do just one thing" - that is a common misconception.
The Single Responsibility Principle:
So "those (many) things that change for the same reason" revolve around the same single responsibility.
Don't Repeat Yourself is another one - it' not about removing repetition or duplication:
Sometimes duplication isn't about the same thing (The Wrong Abstraction):
Also: The SOLID Design Principles Deconstructed (2013)
Basics of the Unix Philosophy: