Technical Insights

Zustand works as a global singleton by default, which creates problems when initializing from props, reusing components like tables on the same page, or resetting state in tests. By wrapping a vanilla Zustand store inside React Context, each component gets an isolated store instance with automatic cleanup on unmount while keeping Zustand's selectors and performance.

A practical introduction to Tail Call Optimization (TCO) discovered while studying recursive algorithms. Explains what makes a call a true tail call, why standard recursion causes call stack overflows with large inputs like factorial(10000), and how refactoring with an accumulator argument enables tail-recursive execution.

Even when recursive code is written with proper tail calls, running it in Chrome or Firefox can still trigger a stack overflow. While TCO is part of the official ECMAScript spec, Safari (JavaScriptCore) is the only engine supporting it. Explores why V8 and SpiderMonkey opted out—due to low practical benefit, lost stack traces during debugging, and security concerns debated in 2016.

Key takeaways from studying frontend architecture for a real-world dynamic codebase refactor. Covers what software architecture means for frontend apps, how to divide features into clean modules without overlap, sketching design diagrams with the C4 model before coding, and understanding the core distinction between Architecture and System Design.