idea

Conceptual integrity is the idea that design should be consistent, predictable, and avoid contradictions. It is mainly a concern for visible design: what users are seeing, i.e. interfaces (API and UI), and manuals ; and requires a single specification philosophy^[2] - including for what is not visible^[3].

The main solution to do so is to have design come from a single person^[1].

links

{todo: link to predictability}

[3]: The law of Law of leaky abstractions makes conceptual integrity important even internally.

references

[1]: Brooks / The Mythical Man-Month:

Conceptual integrity in turn dictates that the design must proceed from one mind, or from a very small number of agreeing resonant minds. [...] By the architecture of a system, I mean the complete and detailed specification of the user interface.

~ The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, Frederick P. Brooks Jr.

[2]: Brooks / The Mythical Man-Month:

Conceptual integrity does require that a system reflect a single philosophy and that the specification as seen by the user flow from a few minds.

~ The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, Frederick P. Brooks Jr.