Travelling across Asia - Our journey from Java to Kotlin
summary
Deliveroo documents a practical migration: start in tests, make the first PR by convert model to data class, use Android Studio’s converter and KAPT for annotation processing, replace utility classes with extension functions, and enforce small, single-commit conversions to avoid merge pain. Expect nullability runtime surprises and imperfect bytecode, hit one major blocker where 100+ Lombok files require manual work, and measure progress — the codebase reaches about 67% Kotlin after two years.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:23From Java to Kotlin
- 2:48Kotlin Tests
- 4:15Kotlin Away Day
- 5:53Kotlin M
- 8:43Finding your pace
- 10:38Code reviews
- 12:33Kotlin Studio
- 14:06Kotlin bytecode
- 16:12Convert job
- 17:54Nullable
- 23:34Reviewing code
- 24:38Lombok
- 25:47What would you change
- 27:27Destress
related talks
33mPragmatic Kotlin on Android
35mPractical Tips For Legacy Java Codebases Conversion Into Kotlin
31mA Kotlin Journey
31mGetting to 100% Kotlin: A practical guide
31mGetting to 100% Kotlin: A Practical Guide
46mThe Road to Kotlintown
39mKotlin, Practically Speaking
16mThe Journey From Legacy Code to Idiomatic Kotlin