From the article:

> All too often, we end up creating lots of shallow modules, following some vague "a module should be responsible for one, and only one, thing" principle.

This is what I'm talking about: this writing is too smart for me, because I can't take any simple answers from it like "modularity" without feeling another part of the article contradicts it with other smart sounding ways of saying don't listen to smart stuff.