The power of Kotlin // Beyond Coding Podcast #28 - Patrick Akil with Paulien van Alst and Urs Peter

Java to Kotlin

Transitioning from Java to Kotlin is often driven by developers who see the benefits of Kotlin's code clarity and reduced boilerplate. Paulien van Alst notes that this shift is typically a bottom-up movement, with developers advocating for the change due to the advantages they experience firsthand 1. This grassroots approach ensures that those who use the language are the ones making the decision, which Patrick Akil believes is crucial for successful adoption.

Ignition always came from developers. And I also just looked at the Kotlin side about statistics and it's about 70% plus comes from developers who want to use Kotlin.

--- Paulien van Alst

Microservice architectures facilitate this transition, allowing teams to experiment with Kotlin in smaller, manageable chunks. Paulien suggests starting with a new microservice or refactoring an existing one, especially if test coverage is high, to gradually integrate Kotlin into the codebase 2.

   

Training Resources

To support teams in adopting Kotlin, various training resources are available. Paulien van Alst mentions that many companies offer training programs, including workshops and educational plugins like those in IntelliJ, which help developers familiarize themselves with Kotlin's features 1. These resources are crucial for teams transitioning from Java, as they provide the necessary knowledge to leverage Kotlin effectively.

There are lots of companies. We both offer training, so we don't want to do any marketing tricks.

--- Paulien van Alst

Moreover, Patrick Akil highlights the importance of having someone on the team who understands the codebase to guide the transition. This ensures that the adoption process is smooth and that the team can intuitively apply Kotlin's paradigms 3.