daneburkland

6 ms·

1. 1.▲
   by daneburkland 6y ago

   Agreed! Always trade offs. Will give that a read. Thanks again.
2. 2.▲
   by daneburkland 6y ago

   Whether the user has switched from "Home" -> "Latest Tweets", whether the app has encountered an error since the request was made, whether the user has interacted with a previously loaded tweet, whether the user has q
3. 3.▲
   by daneburkland 6y ago

   `whateverYouNeedToDo` needs to have knowledge of the application's state. Spreading application logic around event handlers is problematic. In sufficiently complex applications, we're better off simply 'passing messages'
4. 4.▲
   by daneburkland 6y ago

   What do you do inside of the then and error blocks? _That_ is what this post (and state machines) are concerned with. Passing messages to a single entity (reducer in this case) that decides how to handle them, rather than spreading that log
5. 5.▲
   Explicit State Machines in React(afforded.space)

   3 points by daneburkland 6y ago|8 comments
6. 6.▲
   by daneburkland 6y ago

   Totally. Interesting parallel I hadn't considered. Set-it-and-forget-it SaaS is a sweet place to be :)
7. 7.▲
   by daneburkland 6y ago

   Agree, culture is perhaps the elephant in this room.
8. 8.▲
   “Seems like the type of job where you’re only noticed when you make a mistake”(afforded.space)

   32 points by daneburkland 6y ago|4 comments