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!)

Writing efficient unit tests is essential for critical software components. But how do we ensure that our tests are thorough enough to cover a huge variety of typical inputs and most edge cases? I'll introduce you to the concept of property-based testing and share how we benefited from using it at Grammarly.

Writing one component is easy. Conditionally rendering two different ones is still not hard. But what if you face an "n" number of permutations. "n" number of different UI elements and scattered business logic? Switch statements all over the place. Might not sound scary when we write the code. What about your future self? Cognitive load fires off the roof. Maintaining your code? Onboarding new devs? Good luck. Sounds all too familiar? Let's see a possible solution how to tame complexity. How to tackle a large number (possibly infinite) of branches in a frontend codebase without losing our sanity.