Separation of Concerns: Why Should Related Questions Still Be Kept Apart?

Separation of concerns means giving different questions within a complex object their own rules, so each judgement answers only what it is responsible for. It does not claim that the questions are unrelated. It prevents a change in one area from quietly rewriting another.

When writing an article, argument and page styling clearly interact: presentation affects reading, while content affects layout. Yet if changing a font requires rewriting the argument, or revising one sentence requires redesigning the page, the two kinds of work have become entangled. Keeping the text and its presentation separate allows them to be combined for publication while making the reason and consequence of each change easier to see.

The idea is close to cohesion but not identical. Cohesion asks whether the responsibilities inside one part belong together; separation of concerns asks whether different questions retain distinguishable boundaries. Modularity can support that separation, but named modules without clear responsibility rules can still mix concerns. Its value is not merely easier maintenance. It keeps visible what changed, why it changed, and who should judge it.