finite state machines

In this episode, David Khourshid gives the rundown on how finite state machines can make your app more testable, more resilient to bugs, and easier to refactor.

David's initial interest in finite state machines stemmed from his background in music. With music, there is a universal notation that crosses genre boundaries. David thought what if there could be music notation for logic? Well, it ends up people have been trying to figure this out for the last thirty years.

A finite state machine can only be in exactly one state out of a limited number of possible states. The machine can transition to another state through explicitly defined events.

David also chats with Kent about extended finite state machines, how state machines can be used to simplify integration testing, the differences between xstate and redux.

Homework

• Take whatever feature you are working on and model it out in your head as a finite state machine

Resources

• Wikipedia: Finite State Machine
• xstate

Guest: David Khourshid

• Twitter: @davidkpiano
• GitHub: @davidkpiano

Host: Kent C. Dodds

• Website: kentcdodds.com
• Twitter: @kentcdodds
• GitHub: @kentcdodds
• YouTube: Kent C. Dodds
• Epic React: epicreact.dev

Jake and Michael return to discuss the introduction of further type-safety in PHP, BladeX, finite state machines, and rendering HTML emails.

Thanks to Spatie for sponsoring our show.

Show links

• PHP typed properties
• Infinitely better UIs with Finite Automata
• BladeX - custom HTML components in your Blade views
• Introducing view components in Laravel
• Laravel View components (package)
• Maizzle