Introduction to Kotlin: Kotlin Koans Workshop

GDG Chicago
Thu, Jul 25, 2019, 6:00 PM (CDT)

About this event


6-6:30 Food/Socializing/Announcements
6:30-7:30 Introduction to Kotlin: Kotlin Koans Workshop - Led by: Jonathan Bisson and Uddyami Agrawal

About the Speakers:
Jonathan Bisson is a Research Assistant Professor at UIC in the College of Pharmacy. His work is a mixture of drug discovery from natural products (pharmacognosy) and software development. He started using Kotlin around two years ago and it his now his major language (accompanied by a good deal of Python for all the graphics and statistics).

Uddyami Agrawal is an Android Developer with Raise Marketplace. She is serial startup product engineer who specializes in rapid prototyping. She has seen multiple apps, complete their lifecycle from inception to live date. She has done mostly mobile production code but is passionate about full stack development. Kotlin being the new tool she is obsessed with.

About the Workshop:
This tutorial walks you through a series of exercises to get familiar with Kotlin.

Kotlin Koans are a series of exercises to get you familiar with the Kotlin Syntax. Each exercise is created as a failing unit test and your job is to make it pass. You can work with Kotlin Koans in one of three ways.

You can play with Koans online (
You can solve the tasks right inside IntelliJ IDEA or Android Studio by installing the EduTools plugin ( and choosing Kotlin Koans course (
You can clone the project on GitHub ( You can open this project in IntelliJ IDEA, or work with it from the command line using your favourite editor. Note that to work with Koans from Android Studio, use the EduTools plugin.

Whatever way you choose to solve koans, you can see the solution for each task. In the online version and inside EduTools plugin you'll find the button "Show answer". The GitHub repository has two branches, master which contains the exercises for you to do and resolutions which contains the resolved exercises. We recommend checking the solution after you implement the task to compare your solution with the proposed one. Make sure you don't cheat!