Vlad's Roam Garden

Powered by 🌱Roam Garden

composite object interface should be simpler then sum of it's parts

seedling API interface complexity make-public

You create a new object to allow you express a complex concepts or access a complex actions through a simple interface. To make the language of your system more expressive. Rising it's level of abstraction

Producing such interfaces allows us to hide complexity and reduce the cognitive load required to understand the system

good interfaces have small surface area Is a closely related idea -

They allow you to accomplish a lot with the small number of methods and hide their internals as much as possible

reference

people have a very limited short-term memory

Composite Simpler Than the Sum of Its Parts
The API of a composite object should not be more complicated than that of any of its components.
All objects in a system, except for primitive types built into the language, are composed of other objects. When composing objects into a new type, we want the new type to exhibit simpler behavior than all of its component parts considered together. The composite object’s API must hide the existence of its component parts and the interactions between them, and expose a simpler abstraction to its peers. Think of a mechanical clock: It has two or three hands for output and one pull-out wheel for input but packages up dozens of moving parts.
composite object interface should be simpler then sum of it's parts
Growing Object-Oriented Software, Guided by Testsp54

Referenced in

composite object interface should be simpler then sum of it's parts