Code Review · interview question
A bug appears around readability tradeoffs. What is the strongest first debugging move?
Multiple choiceHardchapter-8-curatedpremiumcode-reviewreadability-tradeoffs
totals = [
row["unit_price"] * row["quantity"]
for row in rows
if row["status"] == "ready"
]Answer and explanation
Correct answer
A. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. Compressing critical logic into one expression may impress for a second and then cost hours later.
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?