1. Some background contexts
2. First line of Kotlin
3. Adoption process
4. Is it easy or not?
5. Lessons learnt
6. Where we are now?
Background contexts (facts)
- Starting as MVP project in 5 months
- All Java
- “1-man project”
- 1+ year since Kotlin ofﬁcial support from Google (May 2017)
First line of Kotlin (1)
July 27, 2018
First line of Kotlin (2)
July 27, 2018
Adoption - phase 1 - “the honeymoon”
- Enjoy the language features: data class, extension functions,
out-of-the-box lambda support, collection API, Null-safety!!!,
- Bit by bit: testing code, data object
- The brevity vs the verbosity - clear winner!
- Introduce the language with weighted risks - like you are
driving your car at 60 mph
Adoption - phase 2 - “spreading”
- New components are written in Kotlin
- Converting from Java to Kotlin is encouraged (but
- Supported by: code review process, pair-programming
Adoption - phase 3 - “acceleration”
- First factor: New hire with Kotlin filter (Belarus team expanding)
- Convert from java to Kotlin become a mandatory
- New components are written in Kotlin as always
Is it easy?
1. Java inter-ops capability
2. Rich API collections
3. Reading it in a similar style with Java
4. Functional concepts
- Pair-programming sessions help the adoption become team-friendly and less stressful
- Guild to share the knowledge - via Code Review, filling-water talks,
Where we are now?
Next session - Firechat