API: All People are Important
For non-technical folks, API jargon can seem like another language. But for some API developers and consumers, that’s literally the case. English has, as it has in so many areas, become the de facto language of choice for programming and API development. Read more
In a speech at the 2016 GraphQL Summit, Lee Byron of GraphQL/Facebook put forward a “Secret Master Plan” outlining his hopes for GraphQL, the growing API standard.
In an ideal world, he said, he hoped that GraphQL adoption would look something like this:
The API world is one of constant evolution and mutation. The data that we dealt with in the 1990s is not the same as the data we might deal with in 2017, and because of this, our APIs have had to drastically change in their approaches. Read more
GraphQL has driven much of the conversation around modern API web design, and for good reason — it’s powerful, extensible, and very useful for high data query applications. The ability to request data in a predetermined, knowable format, and the ability to collate endpoints into a single external point, has made GraphQL something that powers some pretty huge projects. Read more
An API provider is akin to a handyman. To fix a specific problem, a specific solution is needed, and a skilled handyman is the only one with the experience, the know-how, and the ability to fix these issues. The same is true in the API space. Read more
