Performance · interview question

A bug appears around profiling first. What is the strongest first debugging move?

Multiple choiceEasychapter-16-curatedpremiumperformanceprofiling-first

bash

python -m cProfile -s cumulative order_ops/cli.py

Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep profiling first implicit so the script stays short and hope the next engineer infers the rule.Solve the symptom with comments only and avoid changing the code shape around profiling first.Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.

Answer and explanation

Correct answer

D. 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. Optimizing the wrong function feels productive and still leaves the real bottleneck untouched.

Test yourself on Performance

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

Start free test

All Performance questions →

A bug appears around profiling first. What is the strongest first debugging move?

Correct answer

Why

More Performance questions