Debugger or logging? Start with the question
A developer uses both debuggers and print-based debugging daily rather than treating them as competing camps.
The takeaway
Choose tools for the state you need to observe.
The context
In a discussion of printf debugging, the commenter offers a simple firsthand account: both approaches are part of their daily work. Our practical synthesis is to define a hypothesis and the evidence needed, then choose an observation method. Unverified project-history claims from the comment are not adopted here.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
Write down the suspected state transition, then choose breakpoints or contextual logs to observe it.
- 02
Remove temporary output after verification and retain useful structured diagnostics where appropriate.
Where this applies — and where it may not
This is personal methodology without comparative measurements; observation can itself affect behavior in concurrent or timing-sensitive environments.
From the discussion
“I use debuggers every day.”
@topspin · View source
Source: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.