🌎 Community-curated list of tech conference talks, videos, slides and the like β€” from all around the world

🎀

A core part of any app is the ability to know at any given time the set of conditions that make up its current operations. As developers, we need to know this for a variety of reasons, including because knowing this tells us whether we should be queuing any changes and gives us the ability to return the user to their current experience should the application display be interrupted. But despite it’s crucial nature, codifying the state of an application at any given point in time can often be messy and error prone work. In this talk, we’ll look at the reasons representing state can be problematic, and some practical ways to make it better.
This page was generated from this YAML file. Found a typo, want to add some data? Just edit it on GitHub.