Kickstarting Kotlin Culture: The Journey from Java to Kotlin
summary
Company moves from a Java monolith to Library Driven Development, breaking the app into 21 repositories and converting 42,000 lines to Kotlin while removing ~14,000 Java lines. First fully Kotlin library is a Twitter query builder (100% Kotlin); a compose feedback feature ships 90% Kotlin. Build and dependency pain is solved with tools Atlas (graphs dependencies) and Pion (topologically ordered pull requests), both originally in Ruby and being rewritten in Kotlin for open source. Guilds, a book club and meetups spread best practices.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 2:08Why am I here?
- 3:02How We Work
- 3:53Potential Risks of Kotlin
- 5:03First Exposure to Kotlin
- 5:55The First Commit
- 6:41Java with Kotlin Syntax
- 6:53Getting More Comfortable
- 7:21Data Classes
- 7:38Rich Collections API
- 7:59Zipping Infinite Sequences
- 8:40Compose Feedback
- 9:13Query Builder
- 10:43Kotlin Love from the Team
- 12:36Kotlin Guild
- 14:26Lazy Sequence Operations
- 14:47Kotlin Book Club
- 15:46Kotlin in Action
- 16:39Building Standards
- 18:05Decomposition into Libraries
- 19:28Library Dependency Graph
- 20:53Tools
- 21:31Current Graph
- 23:02Minor Version Changes
- 24:16Getting Ready for the 1.1 Event
- 24:33Kotlin Meetup Group
- 30:24Change in Libraries over Time
- 33:56Mitigated Risks of Kotlin
- 34:56Conclusion
- 36:30Owly Plush Questions
