Has learning about state machines influenced the way you develop, whether or not you use them directly in your code?

If so, how? I'd love to know!

Fun fact: you can write horrendous-looking code in any library or framework, no matter how good/hyped it is.

Don't judge code by what it looks like, but by what it enables and whether the learning curve is worth it for your team & use-cases.

If we brought back the the @keyframers, what kinds of videos would you like to see most from me and Shaw ( front-end.social/@shshaw )?

A misconception I’ve been seeing conflated switch statements as state machines.

Hand-authored switch statements that process events are *not* state machines, they are more or less inverted computational models.

type Status = 'loading' | 'success' | 'error';

const [status, setStatus] = useState<Status>('loading');

⬆️ This was such a crazy level-up in my React skills when I learned it.

No more boolean explosion. Every state accounted for.

Just add XState and you're set 😉

Okay, this is pretty accurate.

Developers, on average, are short-term thinkers.

Why do so many React developers dislike useReducer()?

Transitioning from pair programming to parasailing React Miami

Got my Java fix (limited edition, signed by Dax Adam ThePrimeagen teej dv 🔭)

React Miami saved the best for last! I’ve never laughed so much in a conference talk, iykyk Jenny Truong David K 🎹

POV: you tried to roll your own auth and realized how painful it is

Clerk React Miami with-heart

I like this framing of xstate/store:

'Like Redux and Zustand had a baby'

If you like super simple, event-driven state management, give it a try!

Fun fact: JSON is valid YAML, which makes YAML both better and worse than JSON

Gonna be honest: for documentation, I just push straight to main. ➡️📚

Removing friction (PRs) makes me more willing to improve and update the docs frequently.

I love seeing state machines in the wild 😍