EmailtheWorld channel: @umich.edu

                        It's hard because side-effects are hard to predict & communicate, especially when working in teams. "Why is there a mutex lock here?" needs to be documented well and, as we all know, documentation rarely stays up to date. But, we need concurrency to get many tasks done at the same time without waiting for each task in serial.

What if, for many tasks, we could get the benefits of concurrency without having to deal with all of those pesky side-effects? That's the promise of asynchronous programming. This episode dives into the whys, hows, and history of async programming!

https://www.programmingthrowdown.com/episodes/184-asynchronous-programming