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.

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 WiggersSwitch to the Mobile Optimized View
© 2026 Created by Michael Levin.
Powered by