The single responsibility principle, as mentioned in the previous post, should be thought of as nothing more than asking the following question:
A class should have only one reason to change.
The question is far simpler than the answer, though. And through this post and the next, I’m hoping to demonstrate exactly that.
But first, I want to mention that the context for this particular question is with a relatively simple API. This doesn’t mean that the result isn’t as beneficial. It does, however, make for quicker reading and more time to talk about the application of the principle.



