Kotlin has been the new superhero on the JVM team for the last couple of years now. With significant support from both JetBrains and the community, Kotlin has managed to find a good balance between new features and understandability.
However, with great power comes great responsibility.
Every new feature holds new ways to shoot yourself in the foot. Every bit of syntactic sugar has the potential to introduce an incomprehensible layer of abstraction.
Amongst all the awesome features of Kotlin, which ones have the potential to harm more than they help? Which ones should you handle with care? How do you make sure that your Kotlin code is not only shiny and new but also genuinely better?
Get ready for the superhero (code)blockbuster of the summer, “The dangerous side of Kotlin”!
- Kotlin basics, OO fundamentals.
Lead Site Reliability Engineer @ Bol.com, Irish folk singer and Space junkie. Equal parts excited bubble of enthusiasm and certified geek, Bart has always had a passion for sharing knowledge. With 13 years of backend engineering experience under his belt, he more and more experienced the necessity for the right level of quality, both in code and in process. To enable that right level, he’s now rolling out SRE as the next evolution of DevOps at Bol.com.