Practical Tips For Legacy Java Codebases Conversion Into Kotlin
summary
Claim: incremental migration with the j2k converter plus manual review yields idiomatic Kotlin rather than verbatim Java syntax. Tools and practices: add Java nullability annotations, run the converter on multiple files to preserve git history, use a git query to pick the top 15 changed files over 12 months, enforce team guidelines with linters/formatters, and automate repetitive refactors. Caveats: platform types cause runtime nullability issues, contracts and DSLs can help but require care, and AI (ChatGPT) speeds conversion but still needs human review.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:26What you need
- 1:11Why Kotlin
- 3:50Conversion Plan
- 10:04Guidelines
- 18:06Get Command
- 23:24Smart Casting
- 24:01Domain Models
- 25:14Usage Classes
- 26:16Typesafe Builders
- 27:38Should I Convert Everything
- 28:43Lazy Features
- 30:07Top Level Functions
- 32:10AI Tool
- 33:13Code Modification
- 33:33Resources
- 33:53Meta Engineers
- 34:04Summary
- 34:26Outro
related talks
16mThe Journey From Legacy Code to Idiomatic Kotlin
19mJava to Kotlin Migration Mistakes
33mPragmatic Kotlin on Android
31mGetting to 100% Kotlin: A Practical Guide
39mKotlin, Practically Speaking
33mTravelling across Asia - Our journey from Java to Kotlin
31mA Kotlin Journey
45mHow we buid and mitigated our Spring Boot applications to Kotlin