Kotlin Coroutines and Concurrency
Coroutines don't have to be asynchronous (or confusing!)
The reason many developers struggle with coroutines in Kotlin isn't because they're inherently difficult to understand. Coroutines are often just introduced in overwhelming ways, diving right into asynchronous code.
But fundamentally, coroutines aren't about asynchronous code. They're about concurrent code. And that's actually way easier to understand.
To show you what I mean, I put together this 6-minute video for you, where I show how coroutines are helpful even in synchronous code.
Know what your coroutines are doing
Once you start using coroutines, you'll face new challenges when it comes to debugging - regular stack traces aren’t much help when the async work was kicked off by code running on another thread.
In this video, I show a few async and coroutine debugging tools you might have missed in IntelliJ IDEA and Android Studio.
Watch out for these coroutine gotchas
Coroutines aren't difficult to understand once you've got the pieces in place, but there are a few gotchas that can trip you up.
In this video, I share a few common bloopers that can take you by surprise if you're not watching for them.
Join the Waitlist
Our Kotlin Coroutines and Concurrency course is just around the corner! Join the email waitlist so you don't miss it.
Join the Waitlist