Our team enjoys coding with Kotlin. In fact, we enjoy it so much we are converting existing Java projects to Kotlin. Most of these Java projects use Lombok, which made us wonder: Would it be possible to use Kotlin’s built-in features to get rid of Lombok?
The answer to this question is more nuanced than the title of this session might suggest. At the end of this talk, you will have enough knowledge to decide for yourself if Kotlin indeed makes Lombok obsolete.
In this talk, we will look at idiomatic Kotlin replacements for Lombok annotations and discuss how these replacements differ from their Lombok counterparts.
- Some basic Java knowledge
Anyone can write code that works. The hard part is building future-proof solutions. As a software engineer at Fresh Minds, my focus is on the latter.
I specialize in building cloud-native microservices with Java, Kotlin, Spring Boot, and everything that comes with it. In recent years, I’ve designed and built multiple data-intensive applications for the government. At the moment, I’m working with a team of Kotlin enthusiasts on projects at Bol.com.
In my spare time, you can find me on the tennis court, and despite having grown up in the flattest country on earth, I love to go skiing in the winter.