Personally I think a good way to set a foot in the door (with Kotlin) is to use it for unit tests. Hey, unit tests aren&#x27;t production code, so what&#x27;s the worst that can happen, right? Plus in many projects - sadly - tests are still perceived as an optional thing.<p>And Kotlin is very well suited for tests, because it&#x27;s so expressive, DSL-friendly etc. There&#x27;s also this pleasant framework: <a href="http:&#x2F;&#x2F;jetbrains.github.io&#x2F;spek&#x2F;" rel="nofollow">http:&#x2F;&#x2F;jetbrains.github.io&#x2F;spek&#x2F;</a><p>If you can&#x27;t convince your team (or bosses) to switch to Kotlin, start writing unit tests in Kotlin. They can even coexist with Java ones, so I believe this is an easy way in. And once people get to see it at work...