Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
20 results across 1 active filter
Page 1 of 1
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Explains stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Connects environment and element injectors to instance lifetime, overrides, lazy routes, and accidental state isolation.
Explains context propagation, value identity, provider scope, domain separation, and measured optimization.
Chooses tag and path invalidation based on data identity, consistency requirements, and affected route surfaces.
Uses ownership, inputs, outputs, rendering responsibility, and dependency scope to define maintainable standalone components.
Uses version-ready notifications, user-safe reloads, cache policy, and deployment compatibility instead of activating mixed versions in place.
Uses latest-request semantics, cancellation, identity checks, and explicit state transitions for changing inputs.
Controls virtual time and completion order to prove debounce, switching, retries, and teardown without sleeping in tests.
Tests user-observable urgent, pending, success, failure, interruption, and out-of-order behavior without scheduler coupling.
Designs optimistic identity, pending state, reconciliation, rollback, and overlapping mutation behavior.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Handles eager subscription, initial values, injection context, errors, cleanup, and repeated conversions.
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.
Separates source state, derived state, and synchronization with external systems to prevent reactive loops.
Connects layouts and templates to navigation, state lifetime, Effects, and deliberate remounting in the App Router.
Chooses between synchronous UI state and asynchronous event streams without treating either model as a replacement for the other.
Distinguishes one-way data, events, and deliberate two-way component contracts without hiding ownership.
Defines a coherent subscription and snapshot contract for state owned outside React, including server rendering.
Diagnoses in-place mutation, equality rules, missing reactive reads, and incorrect use of untracked state.