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.
1345 results
Page 56 of 57
Explains nested ASGI middleware ordering, reverse response flow, exception boundaries, CORS, and streaming-safe design.
Defines a coherent subscription and snapshot contract for state owned outside React, including server rendering.
Uses development-only repeated rendering, Effects, and ref callbacks to expose impurity and missing cleanup.
Connects modern template blocks and stable list identity to DOM reuse, component state, and rendering correctness.
Uses guards for navigation UX while keeping permissions and data enforcement on the trusted server.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Explains how delegation preserves replaceable behavior and narrower coupling while recognizing valid inheritance cases.
Explains code execution during object reconstruction and chooses data-only formats with explicit validation.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.
Explains Java generic invariance through the unsafe write that subtype assignment would otherwise permit.
Separates String immutability from interning and connects both to safe sharing, equality, concatenation, and practical performance.
Diagnoses in-place mutation, equality rules, missing reactive reads, and incorrect use of untracked state.
Treats Alembic autogeneration as a candidate schema diff that still needs semantic and operational review.
Explains migration state, historical model lookup, replay safety, and the limits of migration-time models.
Connects Java's equality and hash contracts to real HashMap and HashSet behavior, including mutable-key failures.
Explains Java lambda capture through copied local values, mutable referenced objects, lifetime, and safe state handling.
Diagnoses lost struct mutations and explains how readonly access can trigger defensive copies.
Uses hierarchy and adjacency to recover context that flat chunks lose while avoiding indiscriminate document expansion.
Explains local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.
Explains how generated text, markup, code, URLs, and tool arguments can become injection or integrity risks downstream.
Keeps JSON binding, validation, writable fields, and response evolution separate from domain and persistence models.
Separates memory visibility and ordering from atomic multi-step updates, avoiding volatile as a substitute for real synchronization.
Places validation, authorization, limits, state transitions, and approval outside the model while acknowledging that guardrails reduce rather than eliminate risk.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.