Code Safety · interview question
A teammate submits shaky mutation and copying code. Which review comment is the strongest?
Multiple choiceHardchapter-3-curatedpremiumcode-safetymutation-and-copying
Answer and explanation
Correct answer
D. Make the rule clearer and easier to explain. Copy or rebuild data intentionally when you need a new version instead of quietly mutating shared state.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Shared mutable structures make later behavior depend on hidden history.
Test yourself on Code Safety
A free test with instant, explained results. No account needed.
More Code Safety questions
- Another engineer will maintain this code later. What choice helps the most around mutation and copying?
- What production risk should you worry about most if mutation and copying is handled lazily?
- A senior interviewer asks for one tradeoff behind mutation and copying. What is the strongest follow-up?
- What do interviewers usually hear as a strong signal when you discuss mutation and copying well?
- When is mutation and copying being used in the wrong way?
- Which option describes the most likely pitfall around mutation and copying?