See this is what I love about finite state machines. You get the ability to see what your states and transitions look like. Not just you, the non-technical peo

See this is what I love about finite state machines. You get the ability to see what your states and transitions look like. Not just you, the non-technical people on a project too. If you can't understand the state machine in your app, there's potential for a lot of unexpected states. FSM flow charts can get dense, but in the same way we compose react components, you can compose FSM's. You don't need a single FSM for your entire application. The router in a react app is often a state machine, and could be a finite state machine. Each major part of you're app could implement it's own finite state machine under that. The value of FSM's is that you can discuss the business logic with your stakeholders, often in language and with visual aids they understand. As opposed to not having it, and just making it up as we go along, and never considering the whole picture. FSM's have helped me explain and reconcile impossible states request by stakeholders (because they didn't understand how they were impossible, because they were sufficiently complex).