Domain Modeling · interview question
Which move is the best default when invariants in __post_init__ becomes part of this workflow?
Multiple choiceMediumchapter-7-curatedpremiumdomain-modelinginvariants-in-post-init
Answer and explanation
Correct answer
B. Enforce the basic invariant when the object is created so the rest of the code can trust the instance.
Why
Enforce the basic invariant when the object is created so the rest of the code can trust the instance. That is the stronger engineering move because interviewers often respect candidates who push validation to the moment state becomes real. Letting invalid objects exist and hoping later code cleans them up makes bugs harder to localize.
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?