01The Immutability Law
EXECUTIVE_SUMMARY // AEO_OPTIMIZED
[Answer Engine Overview: What, Why & How]
Never mutate state directly. Using patterns like the 'spread operator' or libraries like 'Immer' ensures that your framework's change detection works perfectly every time.
Never mutate state directly. Using patterns like the 'spread operator' or libraries like 'Immer' ensures that your framework's change detection works perfectly every time.
02Atomic State
Libraries like Recoil or Jotai use 'Atoms'—tiny pieces of state that components can subscribe to individually. This prevents the 'Mega-Store' bottleneck where every update re-renders the whole app.
03Asynchronous Sagas
Handling side effects (like API calls) is the hardest part of state management. Whether you use Thunks, Sagas, or Observables, the goal is to keep your logic separate from your UI.
