The Single Responsibility Principle and Honest Naming

The solid principles are a set of principles designed to help you build good, maintainable software over time. With this post I’d like to dig into the first one — Single Responsibility.

Single responsibility means that every class you create should do one thing. That lets your classes have a very narrow focus. One of the many benefits is that it lets you compose your classes together more easily than if you have a class that’s doing many things. “Sounds simple!” I hear you say, “Just do one thing and one thing only. Good to go!”