Remote: Kotlin Error Handling & Concurrency with Actors ๐ŸŒŽ

GDG Boston Android
Tue, Jul 14, 2020, 6:00 PM (EDT)

42 RSVP'ed

About this event

This will be a big milestone for the Boston Android community, as we co-host an event with not only GDG Toronto Android, but newcomers:
GDG Bronx
GDG Phoenix Android
GDG Android Columbus
GDG Capital Region
GDG Los Angeles
GDG Silicon Beach
GDG Los Angeles Android
GDG Washington DC
DC Android
Washington DC Kotlin User Group
and Android Budapest too.

Each of us will be posting the same event, with equal amounts of enthusiasm about uniting for the good of all our communities. We cannot wait to see you and, and listen to our wonderful speakers!

Schedule (EDT time zone):
6:00PM - 6:30PM: Introductions
6:30PM - 7:00PM: Error handling in Kotlin and the Result Monad by Adam Bennett
7:00PM - 7:30PM: No Drama Concurrency with Kotlin Actors by Sam Edwards
7:30PM - 8:00PM: Closing

Talk #1: Error handling in Kotlin and the Result Monad by Adam Bennett

Kotlin doesnโ€™t force you to handle functions that might throw exceptions, so how can we best ensure that our code is safe to execute whilst handling errors in a reasonable way? In this talk, weโ€™ll look at some strategies that the team at Cuvva evaluated and discuss in-depth the solution they chose: the Result Monad. Weโ€™ll talk about how it works and build one from first principles, and discuss how utilizing this strategy can help you.
Checkout Adam's blog:

Talk #2: No Drama Concurrency with Kotlin Actors by Sam Edwards

Everything on Android is essentially asynchronous, so achieving thread safety is of absolute importance for the integrity of our data. Historically we've used synchronized blocks and mutexes to achieve concurrency, but the code is complex and sometimes feels unapproachable. Actors are part of the Kotlin Coroutines library and are the most straight forward, readable way to deal with concurrency, without going crazy. This talk will help you understand what Actors and how to use them through real world examples.
Checkout Sam's blog:

The event will be hosted on Remo (, for which a url will be shared within 48 hours of this event.