The Single Responsibility Principle in Software Development

A lot of these are heuristics, right? Like the heuristic that you got at Google is if you're putting the word and in a class name, think about it. And I think a lot of this... I don't know if this is good or bad, but my experience as a software developer has been. A lot of this is almost like an oral history. It gets passed around from developer to developer about here's the things you should generally do, and here's the Things You Shouldn't Do. So yeah, you've picked... That's a perfect example, actually. Unintentionally, because... Almost like a... But they're not different responsibilities.