In fantasy novels knowing the "true name" of anything/anymore gave you ultimate power over them/it. Isn't it the same with naming API Products well? I continue to experience developers seeing "apis" as simply an integration endpoint that has minimal guidance for consumer independence that assumes the consumer has unlimited motivation and patience to drag the details left out of the "api" from the producer. Perhaps that is because most companies don't fully invest in true API Product development, but rather, as a "library" or "integration" interface for a specific software solution!
The Necessity of Naming in APIs
In fantasy novels knowing the "true name" of anything/anymore gave you ultimate power over them/it. Isn't it the same with naming API Products well? I continue to experience developers seeing "apis" as simply an integration endpoint that has minimal guidance for consumer independence that assumes the consumer has unlimited motivation and patience to drag the details left out of the "api" from the producer. Perhaps that is because most companies don't fully invest in true API Product development, but rather, as a "library" or "integration" interface for a specific software solution!