"Then we have no lawful authority to intervene."
By doing so, we've made each class more focused, easier to understand, and easier to maintain.
Instead of thinking about what a class "does," think about who it serves. A module should be responsible to a single "actor" (a group of stakeholders like users or developers). srp main
Imagine the CFO changes the tax calculation logic for calculate_pay . In doing so, a bug is introduced that accidentally breaks the promote logic. The HR department is now blocked by a change made by Accounting.
I slammed my fist on the console. "Initiate the Isolator." "Then we have no lawful authority to intervene
If a single class serves two different actors, it has two reasons to change. If Accounting wants to change the report format and HR wants to change the employee schema, they are both modifying the same file. This is a violation of SRP.
For one elegant, terrifying moment, Everything worked. It routed, billed, predicted, and released. It was the ugliest, most beautiful piece of self-organization I had ever seen. And then it crashed. Imagine the CFO changes the tax calculation logic
No. SRP is not about counting methods. It is about and managing complexity.