The Command Palette Is an Architecture, Not a Widget
The theming article ended on a move from how an app looks to how power users drive it. The command palette — the Cmd+K menu that fuzzy-searc...
Aug 7, 2026
Code-Splitting Is a Boundary Decision, Not a Bundle Trick
The command palette article closed by promising the last piece of this look-and-feel stretch, and it's the one that looks the most like a so...
Analytics Is Architecture: Stop Sprinkling track() Everywhere
This cluster has been about how the parts of an app communicate — event buses for ambient signals, feature flags for toggling behavior. Both...
Feature Flags: Every Flag Is a Branch You Promised to Delete
The event bus article ended on a warning about a certain kind of switch teams sprinkle everywhere with a casual "it's just a toggle" attitud...
The Event Bus: Great for Decoupling, Great for Making a Mess
The last cluster was about making state inside a feature explicit and well-modeled. This one is about what happens between features — how th...
State Machines in React: When Booleans Start Lying to You
Look at a component you wrote recently and count its status booleans. isLoading, isError, isSuccess, isEditing, isSubmitting. Five of them. ...
Undo/Redo Without Losing Your Mind: The Command Pattern in React
The optimistic UI article ended on a small observation that turns out to be a big one. The rollback in onError was a single-step reversal: s...
Optimistic UI: Updating Before the Server Says Yes
At the end of the last article I said that once you hold one coherent copy of server state and can invalidate it precisely, a door opens tha...
Server State Is a Cache: Normalization, Duplicates, and Invalidation You Can Trust
The previous article drew a hard line: state the client owns versus data it doesn't. Everything there was about the stuff you own — theme, d...