Refactoring a Python codebase using the Single Responsibility Principle
Marcelo Lebre
20110

I wonder what do you think about other definition of SRP that states: “A class should have only one reason to change.”. According to this, “doing few things” in one class/function is not necessarily wrong as long as they are not likely to be altered separately. I think splitting virtually EVERY piece of code into smaller chunks to ensure each one of them does one thing actually increases complexity and makes code more rigid, harder to change. What do you think on this matter?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.