Getting to 100% Kotlin: A Practical Guide
summary
Basecamp moves an Android codebase from ~18,000 Java lines to 100% Kotlin over about 430 days, using the JetBrains auto converter plus targeted manual edits. Strategy emphasizes small conversions (models, utilities, adapters), scheduled cooldowns to do bulk work, and a discipline of no new Java. Notes concrete pitfalls: mixed Java/Kotlin duplication, terse unreadable rewrites, and tooling limitations; outcome is a working Kotlin app with measurable progress.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 1:24Kotlin made me happy
- 2:06The unknown
- 2:33Learning the language
- 3:47Start with small conversions
- 5:23No tests
- 6:15Getting excited
- 6:48Where to start
- 8:13Dont be perfect
- 8:58Dont get caught up in it
- 9:33Rabbit holes
- 9:49Code example
- 10:49Dont try to be perfect
- 11:27Kotlin is a big thing
- 11:54Why Kotlin is so good
- 12:37Flow control
- 13:27Extension functions
- 13:59AutoConverter
- 14:43Sidebyside learning
- 14:54Autoconverting
- 15:29Autoconverting is like a moving company
- 16:06Take it to the finish line
- 16:38Use cooldowns
- 17:03Cooldowns at Basecamp
- 18:02No new Java
- 19:16Passing by
- 20:23Recap
- 20:44Ugly Code
- 22:15Curb YourEnthusiasm
- 25:41Code Organization
- 26:34Customers
- 26:56Programmer happiness
- 27:14Customers dont care
- 27:57Take your time
- 29:16Its just a number
- 29:46Thank you
related talks
31mGetting to 100% Kotlin: A practical guide
35mPractical Tips For Legacy Java Codebases Conversion Into Kotlin
31mA Kotlin Journey
42mKotlin Adoption in the Giant Java Application
33mPragmatic Kotlin on Android
33mTravelling across Asia - Our journey from Java to Kotlin
35mAt long last we have Kotlin first at Meta!
16mThe Journey From Legacy Code to Idiomatic Kotlin