In 2016, snapshot testing felt revolutionary. I promoted it everywhere. Then came the backlash: fragile tests, large snapshots, and mindless change approval. The community wasn't amazed. Yet in 2024, Node.js added native snapshot support. Why?

This talk traces snapshot testing's turbulent decade: from Facebook's game-changing release to general rejection, and examines what we got right, what we got wrong, and what place snapshots have today. Spoiler: the story isn't as simple as “snapshots bad”. Let's revisit with clearer eyes.

React has changed a lot in the last year: React 19, 19.1 and now 19.2 brought a stable React Compiler, new hooks like useEffectEvent, the <Activity /> API, and better SSR primitives such as Partial Pre-rendering. And more

In this talk we’ll take a demo React app that’s full of effects, memoization and “old school” patterns, and modernize it step by step

My team ships AB tests constantly. At some point, the codebase started turning into a graveyard of feature flags, dead conditional logic, and TODO comments (or the lack thereof) about cleaning up old experiments. The breaking point: a major component with 4 experiments - hundreds of lines, where changing one thing risked breaking another (which it did). That's when I discovered that custom hooks could be more than reusable logic - they could be containers for isolating experimental code.
Through this talk, I’ll share my experience of using hooks as boundaries for implementing experiments, and how this pattern has improved the way my team can ship features fast while keeping technical debt in check.