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.
237 results across 1 active filter
Page 10 of 10
Distinguishes unavailable conditions, known defects, and unstable tests while keeping lost coverage visible.
Compares eager collections with lazy one-pass generation through memory, timing, reuse, readability, and resource ownership.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Chooses Django view style by clarity, reuse, and lifecycle needs rather than hierarchy preference.
Chooses structural or nominal contracts based on ownership, runtime identity, shared behavior, and third-party integration.
Chooses task synchronization by protected state, notification predicates, and limited capacity.
Compares structured task ownership with ordered result aggregation and different failure behavior.
Compares convenient context-propagating thread offload with explicit executor selection and ownership.
Chooses Django relationship loading from relationship shape, result cardinality, and measured query behavior.
Chooses synchronous or asynchronous FastAPI test clients from the boundary exercised and resources involved.
Chooses a SQLAlchemy abstraction from the work's shape instead of performance slogans.
Aligns SQLAlchemy transactions with business operations and uses savepoints without inventing independent commits.
Balances model methods, QuerySets, managers, and application services by the responsibility they own.
Places exception handling at meaningful boundaries and preserves causes, tracebacks, client contracts, and retry safety.
Diagnoses shared mutable function defaults and explains safe initialization without turning the behavior into a superstition.
Explains Python name binding and patches the reference actually used by the system under test.
Explains Django's nested middleware stack, short-circuiting, exceptions, and response unwinding.
Explains nested ASGI middleware ordering, reverse response flow, exception boundaries, CORS, and streaming-safe design.
Explains code execution during object reconstruction and chooses data-only formats with explicit validation.
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.