@kurtseifried Right, but I feel it's even worse.
The APIs inflation, i.e. polynomial growth of their (ab)use in last years, hides more and more often a bad data structures design, that in modern & politically correct speaking is usually called "interoperability".
@kurtseifried Better still, tools like Stoplight Elements (https://stoplight.io/open-source/elements) make it SO EASY include full-fledged REPL-like functionality in your actual API docs, auto-generating samples using curl and a dozen-plus other methods and letting developers try the API out live from within the docs. I've standardized on using it for all my internal and external APIs, and OMG is it life-changing.
@kurtseifried I agree and I proves that Curl now is more or less the reference implementation example for HTTP methods. Translating from Curl to say Python requests or Unity C# methods is kind of intuitive. The exception is PHP which quite literally implements the low level C API from Curl, a strange and lazy choice IMHO
@kurtseifried I was actually agreeing with you. I have seen tutorials (or worse, trainings) where the exploration of the API's were completely through a UI.
@loke I guess at least we can automatically transcribe stuff now to get the text back. I utterly detest anything that is video first. Video as an addition/alternate, sure, but text uber alles!
Add comment