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.

Madelyn Olson discusses the evolution of Valkey's data structures, moving away from "textbook" pointer-chasing HashMaps to more cache-aware designs. She explains the implementation of "Swedish" tables to maximize memory density. She shares insights on systems intuition, memory prefetching, and the rigorous testing needed for mission-critical caches.
By Madelyn Olson
The Cloud Native Computing Foundation (CNCF) has announced a major evolution of Istio, introducing new capabilities aimed at making service meshes “future-ready” for AI-driven workloads.
By Craig Risi
This article walks you through the Go implementation of Bloom filters to optimize the performance of a recommender. It cover the architectural view, Bloom filter mechanics, Go integration, parameter tuning, and practical lessons learned from making it work under production constraints.
By Gabor Koos
Designed to manage concurrent agents running in containers across local and remote compute, Scion is an experimental orchestration testbed that enables developers to run groups of specialized agents with isolated identities, credentials, and shared workspaces.
By Sergio De Simone
Anthropic's Claude Code CLI had its full TypeScript source exposed after a source map file was accidentally included in version 2.1.88 of its npm package. The 512,000-line codebase was archived to GitHub within hours. Anthropic called it a packaging error caused by human error. The leak revealed unreleased features, internal model codenames, and multi-agent orchestration architecture.
By Steef-Jan Wiggers
© 2026 Created by Michael Levin.
Powered by