Code Reading · interview question
Which boundary choice best fits dry runs and rule narration in a maintainable Python system?
Multiple choiceHardchapter-2-curatedpremiumcode-readingdry-runs-and-rule-narration
Answer and explanation
Correct answer
D. Keep the concern close to the data or API boundary that owns it instead of scattering it across unrelated helpers.
Why
Responsibility should follow ownership. When the concern lives near the right boundary, the system is easier to test and explain.
Test yourself on Code Reading
A free test with instant, explained results. No account needed.
More Code Reading questions
- What production risk should you worry about most if dry runs and rule narration is handled lazily?
- Which option describes the most likely pitfall around dry runs and rule narration?
- A teammate submits shaky dry runs and rule narration code. Which review comment is the strongest?
- A bug appears around dry runs and rule narration. What is the strongest first debugging move?
- If you wrote a test around dry runs and rule narration, what should the test prove first?
- If dry runs and rule narration fails in production, what handling philosophy is strongest?