'Indeed, the ratio of time spent reading versus writing is well over 10 to 1. Best practises Principles Keep it Readable The team library also includes Kotlin in Action which is a slightly heavier read but the first few chapters do a really good job of introducing the major differences between Kotlin and Java. has all the up to date resources to get you started. This document doesn’t go through all the basics.

Safecall handling for nullable values enforced by IDE.Variables have to be explicitly declared as nullable.

Type inference greatly reduces the boiler plate normally associated with that.

There are however some things Kotlin brings to the table that are not shared by all similar languages.

Removing(/hiding) internal inconsistencies that Java has accumulated.

The main benefits compared to developing with Java are similar to other functional languages. In short Kotlin is 'yet another functional JVM language'.

While this document mainly exists for the Wallet team’s internal usage and therefore only covers things relevant to our particular needs it should also provide a starting point for any other team that wishes to develop with Kotlin, particularly on the backend. The purpose of this document is twofold: it has been created to act both as a guide for new developers, especially ones without previous Kotlin experience, on the most important Kotlin specific practises and tools from the perspective of the team and to act as a living document of the various architecture and coding style decisions that the team has made during service development.Įach service will still have their own architecture decision log, but here we will list any non service specific decisions, style guides and general tips that anyone working on our code base should be aware of. Kotlin-guide Kotlin best practises Foreword

Internal keyword in kotlin