Domain Modeling · interview question
Which option is the safer default when shipping code around properties and encapsulation?
Multiple choiceHardchapter-7-curatedpremiumdomain-modelingproperties-and-encapsulation
class InventoryItem:
def __init__(self, stock: int) -> None:
self._stock = stock
@property
def stock(self) -> int:
return self._stockAnswer and explanation
Correct answer
B. Choose the simpler shape that keeps the rule obvious, validated, and easy to observe in logs or tests.
Why
The safest default is usually the one that lowers ambiguity and makes errors easier to diagnose.
Test yourself on Domain Modeling
A free test with instant, explained results. No account needed.
More Domain Modeling questions
- What does a strong engineer do when reasoning through properties and encapsulation code?
- If mini domain model fails in production, what handling philosophy is strongest?
- Which judgment is strongest when choosing a data shape for invariants in __post_init__?
- Which explanation would sound strongest in an interview when discussing instance methods?
- Which option is the safer default when shipping code around invariants in __post_init__?
- A senior interviewer asks for one tradeoff behind instance methods. What is the strongest follow-up?