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.
19 results across 1 active filter
Page 1 of 1
Explains call-site-dependent this binding and compares wrapper, bind, and arrow-function fixes.
Diagnoses forced synchronous layout from interleaved geometry reads and style writes, then batches work and reduces its scope.
Traces synchronous throws and promise rejections through chains, awaits, missing returns, and detached work.
Separates optional, undefined, null, and invalid external data, then narrows values at the correct boundary.
Relates JavaScript classes to prototype-based delegation while preserving the useful semantics class syntax adds.
Explains DOM and CSSOM construction, style, layout, paint, and compositing as a practical performance model.
Uses generics to preserve relationships between types and constraints to express the operations an implementation requires.
Compares JavaScript declarations through scope, initialization, redeclaration, reassignment, and practical default choices.
Chooses interfaces or aliases based on object contracts, unions, composition, declaration merging, and team consistency.
Chooses browser storage by server transport, lifetime, capacity, query needs, sensitivity, synchronization, and offline behavior.
Designs explicit ESM boundaries with focused exports, controlled side effects, and dependency direction that supports safe bundling.
Diagnoses incompatible cached HTML and immutable assets across CDN, browser, service-worker, and rollout boundaries.
Diagnoses aliasing and shallow-copy mistakes, then restores explicit state ownership and immutable update boundaries.
Explains assignability by shape, excess-property checks, and the gap between compile-time compatibility and runtime identity.
Explains closures as functions retaining access to lexical bindings, then connects them to callbacks, factories, state, and common capture mistakes.
Uses derived types for genuine relationships while preserving explicit boundaries for domain and transport models.
Separates declared variable types, unchecked developer assertions, and compatibility checking that preserves useful inferred types.
Chooses promise combinators by success criteria, failure semantics, cancellation needs, and the fate of losing operations.
Prioritizes explicit normalization, strict equality, object identity, nullish handling, and NaN over coercion puzzles.