Debugging · interview question
A bug appears around logging. What is the strongest first debugging move?
Multiple choiceMediumchapter-5-curatedpremiumdebugginglogging
import logging
logging.basicConfig(level=logging.INFO)
logging.info("order sync started", extra={"order_id": "ORD-2"})Answer and explanation
Correct answer
C. 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. Too little logging hides the story, but noisy logs bury the one field or event you actually need.
Test yourself on Debugging
A free test with instant, explained results. No account needed.
More Debugging questions
- When is logging being used in the wrong way?
- Which move is the best default when logging becomes part of this workflow?
- Which explanation would sound strongest in an interview when discussing logging?
- What assumption should be made explicit when working with logging?
- Which move is the best default when tracebacks and root cause becomes part of this workflow?
- A bug appears around tracebacks and root cause. What is the strongest first debugging move?