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.

Platform engineering should have a product focus, as developers are customers; they must provide composable, self-service capabilities, golden bricks rather than rigid golden paths, so teams can move quickly while maintaining consistency. Success is measured through adoption, developer experience, and business outcomes such as deployment frequency and change failure rate.
By Ben Linders
The OpenTofu community released version 1.12.0 on May 14, 2026. This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.
By Claudio Masolo
Google introduced new Android development tools that enable building apps up to 3x faster by using AI agents, including a redesigned Android command-line interface (CLI), structured skills", and an integrated knowledge base. These tools are designed to support agent-driven workflows and are compatible with third-party agents such as Claude Code and Codex, in addition to Google Gemini.
By Sergio De Simone
Backlogs in distributed systems are arithmetic problems, not mysteries. This article provides practical formulas for calculating backlog drain time, sizing consumer headroom, and setting auto-scaling triggers. It covers key failure modes — retry amplification, metastable states, and cascading pipeline bottlenecks — plus when to shed load instead of draining.
By Rajesh Kumar Pandey
Grab’s Central Data Team built a multi-agent AI system to automate repetitive engineering support tasks across its data warehouse platform. The system separates investigation and enhancement workflows using specialized agents coordinated via an orchestration layer. It reduces operational load, improves resolution speed, and shifts engineering effort from firefighting to platform engineering work.
By Leela Kumili
© 2026 Created by Michael Levin.
Powered by