⚛️ In this episode, we have Dan Abramov from Meta!

His work doesn't need an introduction, but the journey to get there is incredible. From learning Visual Basic as an introduction to English, to getting those early formative jobs that shaped his approach & reasoning about problems, to starting with React & getting involved with the community - it's what makes him the person he is today ⭐️

Follow Dan for more 👇🏽
https://twitter.com/dan_abramov
https://github.com/gaearon

⏩ We have Mark Erikson from Replay.io with us today!

Happy to confirm that he does look somewhat like his Simpsons avatar 😄

We talk about how he started in software, which has an origin story from China! Sadly, that's a part of the video that we weren't able to translate 🤷🏽‍♂️

He went from working on government projects in GWT to Backbone eventually to React where things just started to make sense as a representation of UI from state. As a participant in the Flux wars, he went on to work with the Redux community, eventually becoming a core maintainer of the project 🙌🏽

Listening to Mark's journey is inspiring, and it's awesome to hear how he's inspired to work on the next generation of developer tooling at Replay.io, which happened to blow Taz's mind just moments before this interview was shot 🤯

Make sure to follow Mark for more! 👇🏽
https://twitter.com/acemarke
https://blog.isquaredsoftware.com/
https://www.replay.io/

State machines are a useful model for managing complex flows and interactions. This talk will look at the state-of-the art for using state machines in React, when you might want to use them, and when you might want to avoid them. We’ll make use of the library XState, and look at some of the unique developer tooling it can provide (e.g., visualizing all possible states of your code!)

State machines are a useful model for managing complex flows and interactions. This talk will look at the state-of-the art for using state machines in React, when you might want to use them, and when you might want to avoid them. We’ll make use of the library XState, and look at some of the unique developer tooling it can provide (e.g., visualizing all possible states of your code!)