Loading
Pick a focused question that fits your time, stack, and interview goal.
199 results across 1 active filter
Page 9 of 9
Evaluates whether read-heavy access justifies a reader/writer lock instead of a simpler lock or immutable snapshot.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Identifies useful memory and GC signals for alerting without overwhelming the team with noisy telemetry.
Covers the Large Object Heap, big buffers, fragmentation pressure, and practical ways to avoid loading too much at once.
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.
Separates memory visibility and ordering from atomic multi-step updates, avoiding volatile as a substitute for real synchronization.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.