Loading
Pick a focused question that fits your time, stack, and interview goal.
162 results across 1 active filter
Page 1 of 7
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
Traces buffering through the production artifact, proxy chain, compression, cache, platform adapter, and version consistency.
Separates optional, undefined, null, and invalid external data, then narrows values at the correct boundary.
Explains when to derive values during render instead of storing duplicate state that can drift.
Builds a debounced typeahead with latest-request semantics, local error recovery, explicit states, and lifecycle-safe subscription ownership.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.
Implements a reusable ControlValueAccessor with model-to-view updates, touch and disabled semantics, keyboard behavior, and validation-friendly accessibility.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Implements a functional interceptor that adds correlation metadata, records timing, and retries only explicitly safe transient requests.
Builds a route-level Next.js failure UI with safe reporting, retry, and an escape route while keeping expected errors out of the boundary.
Coordinates version-ready events, unsaved-work checks, deferred reload, failure reporting, and one prompt per version without unsafe in-place activation.
Builds writable and computed signal state for filtering and selection while preserving stable row identity and avoiding effect-driven derivation.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Models file validation, progress, cancellation, failure, and retry without losing the selected file.
Explains caching and revalidation choices for static, dynamic, user-specific, and frequently changing data.
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Explains controlled inputs, uncontrolled inputs, validation, refs, and when each form approach fits.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.