Writing better APIs
summary
Shows a concrete workflow: started with an unreadable Ruby PR for a calabash wrapper, cut ~50 lines to ~25, added a unit test that exposed a bug, then fixed behavior and renamed the operation stitching. Describes a Swift component system: 116 components, a new TextConfiguration NSObect with ObjC bridging, strongly typed color/weight types, chainable APIs, and assertions to fail fast. Outcome is testable, documented, and iterated code that actually caught and fixed real bugs.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:17Who am I
- 3:12Questions
- 5:55List class
- 6:59Poor request
- 10:04Naming is hard
- 12:55What we learned
- 14:53The order doesnt matter
- 17:42Measuring success
- 21:39What more can we do
- 24:50Component system
- 27:36Swift
- 35:21Outcome
- 37:34Code
- 41:06Summary
related talks
53mRefactor Your Way Forward
28mUnlocking Seamless Collaboration: Design-First APIs for Components
57mCatching up with Swift
34mShuffle ball change: Sashay your way to clearer API documentation
49mBuilding Software Better: API Lifecycle Management for Developers
24mWriting Stable iOS Applications
29mSpeeding up as an iOS developer
23mAdventures In API Design