Java: Kotlin Not-to-Do List - What we should avoid doing in Kotlin
summary
Advice: always annotate public signatures with explicit public types so Kotlin inference doesn’t leak concrete implementations; hunt down and eliminate platform types from Java interop to avoid hidden NPEs; avoid overusing scope functions and member extensions that hide receivers — prefer explicit this or labeled receivers; choose readable code over clever, dense Kotlin idioms; keep equals/hashCode symmetric and consistent; never make properties do expensive work — use functions and prefer function types over single-method interfaces.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:13Hiding too much in Kotlin
- 14:05Choosing short over readable
- 23:25Disrespecting contract
- 40:36Q&A and closing
related talks
43mIdiomatic Interop
39mTeach Kotlin to play well with Java - Optimization tips for Interoperability
43mFrom Effective Java to Effective Kotlin
38mKids, Play Nice! - Writing With Kotlin-Java Interop
42mFlexible Types in Kotlin
37mEffective Java with Groovy & Kotlin
01h 03mHow Kotlin makes your Java code better
48mKotlin Types: Exposed