I&#x27;m not saying easy to reason about in the sense of &quot;easy to learn because it isn&#x27;t a change from how we used to do things&quot;, but rather, in that it allows one to easily answer:<p>- What is the current state of things?
 - How did we arrive at the current state of things?
 - What should the UI look like given the current state of things?<p>It means that we can say: &quot;Thing A happened, then Thing B happened, then Thing C happened&quot;. And then conceptualize &quot;what should things look like after that chain of events&quot;. I&#x27;ve found this to make errors a whole lot easier about, because I don&#x27;t need to piece together the state when an error happens -- just fire an action that says &quot;An Error happened&quot;, then the stores figure out how to act accordingly. It&#x27;s just another action.