SDK or Not
summary
Argues for shipping curated client libraries versus API-only by walking through a built SDK generator that emits idiomatic clients for JavaScript and Python, shows measured outcomes (integration time drops to half and support tickets fall ~30%), and lists the real maintenance costs: CI for builds, release cadence, and bug triage that add a steady 10–20% overhead. Includes code snippets that failed and the fixes that made the SDKs reliable.
AI-written summary · about
chapters (4)
related talks
30mSDK as the User Interface
24mLet's get started development of API client library
18mSimplifying Consuming APIs for SDK Haters
53mHow not to fuckup with building SDK and make clients happy
30mDeploying and building SDKs as a service Developer
34mWhy SDK Docs Matter — And What I’m Doing About It!
22mSDKs, Relations, Love & Thunder
54mLessons Learned From Maintaining SDK in Python for Three Years