Interfaces: Why Does Connection Begin with Constraints?

Interfaces: Why Does Connection Begin with Constraints?

An interface is not merely the place where two things meet. It is a limited set of agreements that lets them work together reliably. A plug specifies shape, voltage and contacts; a software interface specifies which requests may be sent and what results will be returned. The clearer the agreement, the less each side needs to know about the other’s internal workings.

This distinguishes an interface from a connection. A connection only indicates contact; an interface also defines what counts as valid contact. Nor is it simply a boundary. A boundary preserves difference, while an interface selectively permits exchange without dissolving that difference.

An interface appears to restrict freedom, yet it actually reduces the cost of coordination. If every collaboration required complete knowledge of the other side, any internal change could disturb the whole system. With a stable interface, internal parts may change while the outward agreement remains intact. A good interface does not expose everything. It exposes only what the relationship needs. It protects difference while allowing differences to cooperate.


Discover more from Geoffrey Chen

Subscribe to get the latest posts sent to your email.