Loading
Pick a focused question that fits your time, stack, and interview goal.
11 results across 1 active filter
Page 1 of 1
Explains caching and revalidation choices for static, dynamic, user-specific, and frequently changing data.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Moves non-deterministic browser-only rendering behind a stable server snapshot and post-hydration update.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
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.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
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.