Code Review · interview question
What is the clearest sign that code around readability tradeoffs should be refactored?
Multiple choiceHardchapter-8-curatedpremiumcode-reviewreadability-tradeoffs
Answer and explanation
Correct answer
A. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Choose the form that another engineer can review and debug confidently, even if it uses a few more lines.
Test yourself on Code Review
A free test with instant, explained results. No account needed.
More Code Review questions
- What production risk should you worry about most if abstraction discipline is handled lazily?
- Another engineer will maintain this code later. What choice helps the most around readability tradeoffs?
- A senior interviewer asks for one tradeoff behind abstraction discipline. What is the strongest follow-up?
- When is review quality being used in the wrong way?
- What does a strong engineer do when reasoning through readability tradeoffs code?
- What kind of contract clarity matters most for abstraction discipline?