Debugging · interview question

What is the healthiest performance judgment around tracebacks and root cause?

Multiple choiceMediumchapter-5-curatedpremiumdebuggingtracebacks-and-root-cause

python

def line_total(price: float, quantity: int) -> float:
    return price * quantity


print(line_total("9.99", 3))

Solve the symptom with comments only and avoid changing the code shape around tracebacks and root cause.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep tracebacks and root cause implicit so the script stays short and hope the next engineer infers the rule.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Answer and explanation

Correct answer

D. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Why

Premature optimization is usually weaker than targeted optimization backed by measurement.

Test yourself on Debugging

A free test with instant, explained results. No account needed.

Start free test

All Debugging questions →

What is the healthiest performance judgment around tracebacks and root cause?

Correct answer

Why

More Debugging questions