I teamed up again with Tomek Ducin for a hands-on look at front-end state management using React Query (now Tanstack Query). We cover how separating local UI state (like toggles and forms) from server data prevents stale info, redundant fetching, and messy code. Tomek showed how React Query can encapsulates: caching, time-to-live, and refetching and other stuff you shouldn't be implementing on your own. He also showed the overlap with backend patterns like pub/sub, proving these concepts span the entire stack.

Architecture Weekly's publication is a central hub for architecture enthusiasts, offering insights into architectural design, urban planning, and sustainable architecture practices. Through articles, case studies, and architectural critiques, Architecture Weekly offers insights into iconic buildings, architectural trends, and innovative design solutions. Readers can learn about architectural history, design principles, and environmental sustainability initiatives to gain a deeper understanding of the built environment and its impact on society. Additionally, Architecture Weekly provides updates on the latest architectural projects, design competitions, and industry events to help architects and designers stay informed and inspired.

Architecture Weekly

Tomasz Ducin provides an in-depth guide on using React Query for frontend state management, highlighting its capabilities in handling server data, caching strategies, and UI updates. He explains the importance of distinguishing between local UI data and server-fetched data to maintain a clean structure. Although originally from the React community, React Query (now Tanstack Query) is compatible with other frameworks like Angular.

React Query: A solution for Frontend State Management challenges? With Tomasz Ducin

<p>That video player is absolutely cancerous</p>
