Debugging · interview question
Which naming or modeling choice is strongest for logging?
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. 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.
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?