Everything is an API
summary
Argues that every module is an API and gives concrete patterns and outcomes: favors interface-first composition with small granular contracts, uses Kotlin features like internal implementations, suspend and infix to communicate intent, and applies Gradle tooling — especially Gradle Enterprise build cache and scans — to measure effects. Describes migrating to modularisation (faster incremental builds, some clean-build overhead), prefers implementation over API for dependencies, uses deprecated replaceWith and custom annotations to manage breaking change rollouts, and reports these practices as practicable with careful tradeoffs.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:54The downsides
- 4:03The double standard
- 5:39The enemy of good
- 7:23Obstacles
- 7:47Implementations
- 9:42Code Smell
- 11:49Naming
- 15:34Inherent
- 17:39Impact Analysis
- 20:44Pitfalls
- 23:44Conclusion
- 25:26QA
- 28:16Best practices
- 30:37Implementation vs API
related talks
54mBreaking Down Your Build: Architectural Patterns For A More Efficient Pipeline
27mBuilding Great Web APIs
26mAPI archaeology: guiding the API journey
42mGood APIs don't need a tutorial
38mCrafting Idiomatic APIs with Kotlin and Compose
42mEvolving your Kotlin API painlessly for clients
40mThe API mindset: tech, product, business and legal
49mBuilding Software Better: API Lifecycle Management for Developers