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.
32 results across 1 active filter
Page 2 of 2
Places invariants and state transitions near the data they protect while keeping orchestration and infrastructure out of domain entities.
Evaluates repositories by domain language, query ownership, and substitutability instead of treating them as a mandatory wrapper around DbSet.
Explains how callers use one contract while runtime dispatch selects implementation, then connects that mechanism to extensible behavior.
Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.
Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.
Uses static members for type-wide stateless behavior and constants while avoiding hidden global mutable state and lifetime problems.
Moves invariant-sensitive decisions toward the owning object while keeping orchestration, queries, and cross-boundary work appropriately explicit.
Chooses code organization from change locality, shared policy, and cross-cutting needs rather than adopting one folder structure universally.