# 90 Days of Kotlin

DevFeed: [90 Days of Kotlin](<https://devfeed.tech/articles/90-days-of-kotlin-19821.md>)

Original publisher: [Read original article](<https://tech.gc.com/90-days-of-kotlin/>)

Author: GameChanger

Published: 2019-07-10T17:13:53Z

Content type: article

Language: en

Sources: [GameChanger](<https://devfeed.tech/sources/gamechanger.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Java](<https://devfeed.tech/topics/java.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [Android](<https://devfeed.tech/topics/android.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [java](<https://devfeed.tech/tags/java.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [programming](<https://devfeed.tech/tags/programming.md>)

## AI overview

A developer reflects on 90 days of using Kotlin after years of Android development with Java. The article presents Kotlin as a practical evolution within the JVM ecosystem, emphasizing its interoperability with Java, reduced boilerplate, compiler-assisted features such as type inference and smart casts, and standard-library conveniences.

## Source excerpt

Riding the wave of change Old habits die hard. We're creatures of habit, and provided there's no stimuli that causes us to change and evolve, we'll all very likely stay static. After all the more you repeat something, the better you get at it, and there's little to be gained from change for change's sake save for a new perspective, which can be rather varied in its returns. I've been an Android Developer for a little over 5 years now, and I love Java. Quite a bit actually; its APIs for common data structures, its explicitness and the way it makes it easy to read someone else's code, its OOO approach and how it lends to easy encapsulation and delegation to class instances, its recent adoption of a pseudo functional paradigm with functional interfaces and single abstract methods... the list goes on. Not only does it offer all this, but it does so while being backwards compatible with previous versions of the language. It's therefore not surprising Java and the JVM form the thriving ecosystem they are today. I've spent a considerable amount of time learning about the language and its design decisions and they all seem extremely justifiable to me. However, the programming world moves fast, and with Google embracing Kotlin more and more each year, I needed not only to switch, but to be in an environment that I could use Kotlin in, day in and out. Here at Gamechanger, I've found that, and have been learning and using Kotlin for the past 90 days, and there's quite a lot to like. Fundamentally Kotlin doesn't try to re-invent the wheel, nor is it some great departure from Java that would cause an epic schism or anything of the sort in the JVM ecosystem. If anything, it readily embraces its heritage with 100% interoperability with Java. What Kotlin seeks to do instead, is get out of your way, and let you do as much as you already could with a lot less effort and code. Compiler niceties A lot of what Kotlin does I've found, is to take things the compiler could do, and simply mak