Kotlin Not-to-Do List - What we should avoid doing in Kotlin
summary
Kotlin code warns against hiding important details: declare public API types instead of relying on type inference (author once had to read bytecode to find a type), eliminate platform types to avoid mysterious NPEs that can propagate from Java. Avoid implicit multiple receivers and member extensions, prefer explicit receivers. Favor clear if/when over dense safe-call+Elvis chains, never use nullable Unit or operator overloading for unclear semantics, keep visibility minimal, implement equals/hashCode consistently (returning constant hash leads to millions of extra comparisons).
AI-written summary · about
chapters (6)
- 0:00Introduction to Kotlin not-to-do list
- 1:17Hiding too much in Kotlin
- 12:00Shortcuts over readability
- 21:31Disrespecting contracts in Kotlin
- 39:42Function types vs interfaces
- 41:03Summary of Kotlin sins
