The Dangerous side of Kotlin
summary
Kotlin features deliver real power but also concrete hazards: extension functions produce three different asUrl extensions in one codebase, scattering behavior and breaking encapsulation; operator overloading was used to model stock valuation (weeks of work) where a × b actually performs complex, non‑commutative enrichment and confuses new engineers; an attempted money inline class solves representation but exposes when operators are appropriate; a Pub/Sub emulator setup built with lambdas‑with‑receiver compacts code but hides scope and forces IDE dependence. Numbers: a 700‑engineer backend, 10M customers, hundreds of thousands of daily packages.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 4:03Kotlin as dangerous tool
- 9:07Extension functions risks
- 15:26Operator overloading dangers
- 22:07Lambdas with receiver pitfalls
- 27:32Right tool for the job
