Faris Aziz is a Staff Frontend Engineer specializing in React, Next.js, monetization systems, and resilient web architecture. He's led teams in early-stage startups and scaling companies, built career ladders from scratch, and shipped systems used by millions. His work spans greenfield builds and legacy refactors across Fintech, SaaS, Fitness, and Connected TV, with companies like Smallpdf, Fiit, Discovery, GCN, and Navro. He focuses on building performant, user-centric applications with solid observability and maintainability. Faris co-organizes ZurichJS, contributes to tools like Raycast, and spends time contemplating life's great questions, like why the build works on his machine but nowhere else.
Most teams fight React performance with memoization band aids and prop drilling acrobatics.
We obsess over useMemo and useCallback, sprinkle React.memo everywhere and hope for the best. Yet performance problems keep surfacing. The root issue is usually not a lack of memoization; it is a misunderstanding of component architecture.
This talk dives into how React’s reconciliation works, and how combining it with Atomic Design principles gives you a natural performance model without escape hatches. By structuring components around stability boundaries and predictable render surfaces, you avoid unnecessary re-renders from the start and remove half the memo calls currently in your codebase. I will show real examples at scale, common reconciliation traps, measurable outcomes when refactoring with atomic boundaries and how to test and profile effectively. You will leave knowing where React pays attention, how to design with reconciliation in mind and why deleting memoization more often than not is in your favor.
Searching for speaker images...