Uploaded April 2026 | Updated September 2026, 3 weeks ago
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.
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.





![Are We Ready For The Next Cyber Security Crisis Like Log4Shell? by Soroosh Khodami
AI era is bright, but full of terrors!
In a world where vulnerabilities like Log4Shell, Spring4Shell, and the XZ Backdoor make headlines, securing our software ecosystem has never been more critical. In this session, Soroosh, a hands-on architect with experience working on security platform services for large enterprises like Rabobank, will share practical strategies and best practices for securing the software development process, applicable to both small startups and large organizations.
Key takeaways and questions that will be answered in this session:
- [Live Demo] What is a Supply Chain Attack, and how dangerous can it be?
- An example of lateral movement that begins with a basic SQL injection attack and escalates to gaining root access to a Kubernetes cluster
- Exploring new attack vectors in the AI era and the defense strategies to detect, prevent and mitigate them
- Most effective practices to secure your CI/CD process
- Practical strategies on how Software Bill of Materials (SBOM) help us prepare for the next Log4Shell crisis?
- What does DevSecOps mean, and what is its main objective? Are We Ready For The Next Cyber Security Crisis Like Log4Shell? by Soroosh Khodami](https://i.ytimg.com/vi/rV7MIxFKSDI/mqdefault.jpg)




