Loading
Pick a focused question that fits your time, stack, and interview goal.
48 results across 1 active filter
Page 2 of 2
Explains client cache keys, freshness, invalidation, refetching, optimistic updates, and server truth.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
Uses discriminated unions to represent valid UI states and make transitions exhaustive.
Guards a mutation immediately, exposes pending state, and restores the command after failure.
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
Explains stale closures in callbacks, effects, timers, subscriptions, and how to fix them cleanly.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Explains Next.js server/client component boundaries, interactivity, data access, serialization, and bundle impact.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Explains server rendering, client rendering, static rendering, freshness, SEO, personalization, and performance trade-offs.
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Tests one browser-to-database practice workflow with isolated fixtures, resilient locators, durable assertions, and reliable cleanup.
Explains component tests that assert user-visible behavior instead of implementation details.
Explains when a reducer clarifies related state transitions and when independent state remains simpler.
Explains route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Explains why external data needs runtime validation even when the application uses TypeScript.