Loading
Pick a focused question that fits your time, stack, and interview goal.
81 results across 1 active filter
Page 3 of 4
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
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 frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
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.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
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.
Persists a job and outbox command before returning a status URL for long-running work.
Produces field-keyed validation errors through one reusable endpoint boundary.
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.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
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.