Debugging · interview question
What does a strong engineer do when reasoning through logging code?
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. Narrate the data shape, the state changes, and the exact rule order step by step.
Why
Interviewers often use simple code to test whether you can reason through execution without bluffing.
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?