Performance · interview question

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

Multiple choiceMediumchapter-16-curatedpremiumperformanceprofiling-stories

python

def profile_first() -> None:
    print("measure before rewriting")

Delay clarity until production traffic reveals the edge case and then patch it under pressure.Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.Keep profiling stories 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 stories.

Answer and explanation

Correct answer

B. 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. Vague claims that code is now 'optimized' sound weak without numbers or a causal explanation.

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 stories. What is the strongest first debugging move?

Correct answer

Why

More Performance questions