#system #system-failure #unintended-consequence #api #software #design


Also called Hyrum's law, the law of implicit interface states that all behaviors of your APIs, be them voluntarily or not, will be depended upon, and therefore create friction to change.

The consequence is that foresee-able changes (such as leaky abstractions) should already be accounted for, and changes for APIs with significant number of consumers, even when seemingly internal, should be executed through change management (and versioning of the API).

Examples are: