Preface
The importance of maintainability, writing code that communicates intent and maximizes compiler involvement, and how this is reflected in the Kotlin Primer.
— — — — — — — — — — — — — — —
THE CURRENT VERSION OF THIS ARTICLE IS PUBLISHED HERE.
— — — — — — — — — — — — — — —
Before we dive into the Kotlin language, I would like to take some time to explain what drove me to write the Primer in the first place. After all, Kotlin comes equipped with fairly extensive documentation, and the internet is chock-full of material, so why bother writing yet-another-Kotlin-resource? This article will attempt to answer that question, explain (one of) the objectives that guide the way the material is presented, and explain why I chose this specific objective.
From time to time in this article, I will be referencing certain features of Kotlin, which, if you are a Kotlin freshman, you will not understand! So let me put you at ease right away — there is no need to understand what they are. Feel free to ignore them and keep reading, they’re only there for context and aren’t important to understand the rest of the text.
