Codetown ::: a software developer's community
Part 1: https://codetown.com/group/kotlin/forum/topics/kotlin-thursdays-ima...
Part 2: https://codetown.com/group/kotlin/forum/topics/kotlin-thursdays-ima...
Welcome to Kotlin Thursdays! Last week, we figured out how to write primitive filters and apply them to our images with the or function. This week, we look at refactoring with higher-order functions.
Think of these resources as supplemental if you happen to be more curious. We always encourage looking into documentation for things you use!
We could continue to write individual functions that feeds 2 images and a particular function, but in Kotlin, we have the ability to use a single function that accepts 2 images and a function with the help of higher order functions. Below, you can see how similar our orFilter function and makeDuller function is.
In programming, programs may take data as parameters and pass those parameters into the function to return a different output or alter the behavior of a program. Kotlin is a functional language, and one characteristic of a functional language is that functions are also able to treat functions as data. You can pass a function as a parameter, which is really powerful!
A higher-order function is a function that may take functions as parameters. You can pass a function with double-colon (::). Double-colon (::) is used to get function (callable) reference in Kotlin.
Ruby facilitates higher order functions with yield, which involves passing a block to a method.
Like Ruby, Kotlin treats functions as first-class citizens, which is a pillar of functional programming. In Kotlin, the equivalent of block code is known as lambda functions, indicated by the pattern:
Instead of passing the object as an argument, you invoke the lambda variable as it if were an extension function. Haskell also has higher order functions which can designate the kinds of parameters a function may take within a function.
In this case, we are going to work with a general function, as opposed to an extension function that is invoked with a qualifer.
The function we write will take a filter function and 2 pixelReaders. Our function parameter, in particular, will only accept functions that take 2 Color parameters and returns a Color.
So here, the input function that accepts the 2 parameters is the receiver type, the output Color receiver object.
fun applyFilter (filter: (Color, Color) --> Color, a: PixelReader, b: PixelReader): PixelWriter {
for (x in 0 until width) {
for (y in 0 until height) {
resultWriter.setColor(x, y, filter(a.getColor(x, y), b.getColor(x, y))
}
}
return resultWriter
}
I hope you all had fun learning a little bit about image processing! Keep exploring and creating new image filters and maybe even as a challenge, think about how you might implement an RGB system to create image filters for colors. Until next time :)
Tags:
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.

AI poses major challenges for green IT: each query consumes vast energy, GPU chips last only 2-3 years, and costs stay hidden from users. Regulatory frameworks like the EU AI Act fall short on enforcement, Ludi Akue said. In her talk What I Wish I Knew When I Started with Green IT she presented model compression, quantization, and novel architectures, using sustainability as a design constraint.
By Ben Linders
AWS introduced account-regional namespaces for S3, fixing global bucket name collisions that broke IaC automation for 18 years. New format: {prefix}-{account-id}-{region}-an. CloudFormation gets the BucketNamePrefix property, and IAM gets the s3:x-amz-bucket-namespace condition key. Prevents confused-deputy attacks by making names unpredictable when there is no account ID.
By Steef-Jan Wiggers
Andrew Davidson and Akshat Vig discuss the journey of disrupting the transactional database market. They explain why the document model became the "Buckminster Fuller" moment for modern apps and share lessons on scaling from "web-scale" memes to mission-critical workloads. Leaders will learn about operational excellence, monetizing convenience over control, and navigating the open-source race.
By Akshat Vig, Andrew Davidson
In the GenAI era, code is a commodity, but alignment is not. Traditional review boards can't scale with AI-generated output. This article explores "Declarative Architecture" - transforming ADRs and Event Models into automated guardrails. Move beyond "dumping left" to a model where the conformant path is the path of least resistance, enabling decentralized governance without losing cohesion.
By Kyle Howard, Christian Johansen, Dana Katzenelson, Brian Rhoten, Warren Gray
At QCon London 2026, Ivan Zarea, Director of Platform Engineering at Netlify, discussed the impact of AI on web development, noting a surge in non-traditional developers among the 11 million users on the platform. He presented three pillars for developer tools: developing expertise, honing taste, and practicing clairvoyance, emphasizing the need for thoughtful architecture in a evolving landscape.
By Daniel Curtis
© 2026 Created by Michael Levin.
Powered by