The Single Responsibility Principle for Object-Oriented Design

If we're grouping things based on their reason to change, what are the names that I'm going to end up with? Well, you'll wind up with longer names generally, but very focused. For example, the class that saves the employee to the database. You might call this the employee gateway using Martin Fowler's gateway pattern. And by the way, this practice goes right down to the function level as well. We want to have lots of little functions, not few big Functions.