Codetown ::: a software developer's community
Part 1 here: https://codetown.com/group/kotlin/forum/topics/kotlin-thursdays-kot...
Welcome, all to another week of Kotlin Thursdays. In this week we are going to dive deeper into Kotlin Koans and like all koans, this one is going to get more difficult. This week we are going to cover default arguments, lambdas, strings and data classes. These koans are a great way to get into functional programming and learn about the kotlin syntax.
Within default arguments, we are going to you will see how kotlin can take declare an argument at the beginning of the function. Using this notation at the beginning of the function for some makes the code easier to read and support. Having the declarations at the top also reduces the lines of code so there is less sifting through lines. I learned how to do this type of declarations earlier and I always preferred that style.
Lambdas are still confusing to me. My first introduction into lambdas was playing with them on Amazon Web Services. I then saw that lambdas popped up in Java 7 and 8. I’m glad I can see them again here. I was a little confused about the “it” convention which confused me. When I read through the function from right to left the use of ‘it” makes perfect sense.
Strings glorious strings yes I sing this out loud often. This koan teaches us about string literals and string templates and how to use them. I weird but for some reason, this koan makes me happy. I think when I started down my Kotlin journey this is where things started making sense to me.
The last koan we explore is the data class. Within the data class koan we see some the readability of Kotlin shine. We are given a class in java and then rewriting the class in kotlin and as you might have guess writing in Kotlin is cleaner.
I hope you enjoy the Kotlin Thursdays episode!
For this walkthrough, you will need to install the EduTools plugin into IntelliJ!
https://www.jetbrains.com/help/education/install-edutools-plugin.html?section=IntelliJ%20IDEA
Here is another overview of what we are doing -
https://www.jetbrains.com/help/education/learner-start-guide.html?s...
Think of these resources as supplemental if you happen to be more curious. We always encourage looking into documentation for things you use!
Tags:
Super! Can’t wait to work through it!
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Dynamic principal engineer at Netflix, Kasia Trapszo, expertly navigates the evolution of the company’s commerce architecture from a DVD rental service to a global streaming giant. Her insights on pragmatic adaptations to billing systems reveal invaluable lessons on agility, localization, and the complexity of modern payment landscapes.
By Daniel Curtis
At QCon London 2026, Lan Chu, AI Tech Lead at Rabobank, shared lessons from deploying a production AI search system used internally by more than 300 users across 10,000 documents. Her experience shows that most failures in RAG systems stem from indexing and retrieval, rather than the language model itself.
By Daniel Dominguez
At QCon London 2026, Suhail Patel, a principal engineer at Monzo who leads the bank’s platform group, described how the bank has built a developer platform capable of shipping hundreds of changes to production every day.
By Matt Saunders
At QCon London 2026, Ian Cooper, senior principal engineer at Just Eat Takeaway, discussed managing asynchronous APIs in production, showing how endpoint definitions can drive code generation, schema registration, and the automation of messaging infrastructure.
By Renato Losio
JP Morgan Chase engineers Luis Albinati and Surabhi Mahajan argued that multi-cloud complexity can't be solved with engineering alone. Speaking at QCon London, they showed how treating multi-cloud as a product with capability mapping, demand governance, and defined users tames the chaos.
By Steef-Jan Wiggers
© 2026 Created by Michael Levin.
Powered by