Ivanās first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didnāt know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Hereās how this is going to work. Weāll take a slow app ā debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) ā pinpoint the bottleneck ā and then repeat, several times more. We wonāt talk about the solutions (in 90% of the cases, itās just the olā regular useMemo() or memo()). But weāll talk about everything that comes before ā and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work ā but want to get better at using the performance tools around React. Also, weāll be covering interaction performance, not load speed, so you wonāt hear a word about Lighthouse š¤)
Comments