Separation of concerns doesn’t need to be boring
Softwares are subject to change all the time, and one aspect that contributes to defining the quality of a code is precisely how easy it is to be altered. But what makes it be like so?
…if you’re afraid to change something it is clearly poorly designed.
— Martin Fowler
“Gather together the things that change for the same reasons. Separate those things that change for different reasons.”
In software development, a responsibility is a task that a unity is committed to achieving, for example: represent the concept of a product in an application, handle network requests, persist a user in the database, and so on and so forth.
... read the whole story at blog.codeminer42.com.