Debugging · interview question
What is the healthiest performance judgment around 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
B. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.
Why
Premature optimization is usually weaker than targeted optimization backed by measurement.
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?