Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 22 of 29
Builds a story about taking feedback seriously and changing behavior in a visible way.
Explains stale closures in callbacks, effects, timers, subscriptions, and how to fix them cleanly.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Implements safe redaction of known sensitive keys in a dictionary before logging.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Replaces a parent query plus one status query per row with one server-side projection.
Uses metadata-driven behavior deliberately and protects reflection-dependent code when publishing with trimming or ahead-of-time compilation.
Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
Explains when production approvals are useful and how to avoid turning them into empty bureaucracy.
Explains how to trace a production deployment back to commit, build, artifact, configuration, and approval.
Ranks duplicate import rows, previews the deletion set, and removes older copies with deterministic retention.
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.
Evaluates repositories by domain language, query ownership, and substitutability instead of treating them as a mandatory wrapper around DbSet.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Handles the request body as a forward-only resource, buffers only when necessary, and enforces limits before large input consumes the service.
Uses a conditional update and transaction to prevent overselling while recording the reservation consistently.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Coordinates server retry signals with client backoff, deadlines, idempotency, overload protection, and bounded retry budgets.
Implements a bounded async retry helper that respects cancellation and does not retry every exception blindly.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.