Good APIs don't need a tutorial
summary
Argues that a library should teach by arrangement not text: split an API into its own tiny module so compilation is fast and experimentation happens in a side fast iteration cycle (used at CashApp and with SQLDelight), generate clients from proto with gRPC/Wire 3 to avoid brittle retrofit setups, design APIs so IntelliJ autocomplete guides correct use, prefer typed, math‑based layouts (contour) over fragile constraint editor workarounds to make errors visible and discovery immediate.
AI-written summary · about
chapters (23)
- 0:00Introduction to talk
- 1:23Gaming and coding origins
- 4:33Fast iteration in game design
- 6:57API placement for fast iteration
- 9:03Iteration cycle in APIs
- 10:06No tutorials in game design
- 11:29RecyclerView adapter lesson
- 14:15Portal and tutorial design
- 14:57Xenoblade Chronicles 2 critique
- 16:21Retrofit vs gRPC APIs
- 18:07Halo's on-rails tutorials
- 19:31Constraint layout exercise
- 23:19Simple not easy concept
- 24:00Math-based layout with Contour
- 26:46Relevant autocomplete menus
- 27:08Deprecated annotation usage
- 28:32Extension function scoping
- 31:20Tools near problem areas
- 34:07Rewarding not punishing APIs
- 37:16Building API communities
- 39:02Play your own game
- 40:03Recap of lessons
- 40:44Role of tutorials in APIs
