Debugging · interview question

Which naming or modeling choice is strongest for 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.Keep tracebacks and root cause implicit so the script stays short and hope the next engineer infers the rule.Use names and structures that describe the business fact directly instead of temporary implementation noise.Delay clarity until production traffic reveals the edge case and then patch it under pressure.

Answer and explanation

Correct answer

C. Use names and structures that describe the business fact directly instead of temporary implementation noise.

Why

Clear naming and modeling shorten debugging, review, and onboarding time.

Test yourself on Debugging

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

Start free test

All Debugging questions →

Which naming or modeling choice is strongest for tracebacks and root cause?

Correct answer

Why

More Debugging questions