Talk type: Game
Speakers will show code with coroutines and ask what should happen in it, and listeners will choose their answers. After that, we'll run the live code and evaluate what actually happened. Then there will be a parsing of why things are the way they are. Whoever gets the most answers right wins.
There will be examples with synchronization and competitive work, abolition of coroutines and non-obviousness of Kotlin Flow.