Virtual Track sessions will be available on-demand on the
OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions
here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the SessionsJoin the OAI Slack WorkspaceOnce you’ve joined Slack, join the
#asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!
---------------------------------------------------------------------------------------------------------------------------------------------------
Generating SDKs and Code Samples from API specifications is a common practice among API providers. The generated code is considered as a wrapper over the API specification, and often lack the depth of a production-quality code. On the other hand, some hand-written SDKs offer quality code and valuable features such as time-outs, caching and retries. However, manual SDKs are hard to maintain, so the debate over auto-generated vs manual ones continues.
In this talk, I will be covering the developer requirements for idiomatic and production-ready code, and how can those requirements be made part of an API specification. For SDKs or client libraries, my focus would be taking them beyond API-wrappers by adding the layers of developer experience, both for API consumers and providers. At the end, I will elucidate the limitations of the specs-generated code samples, and a few thoughts to make them usable in production.
