What does this mean:
* Invest in tools and training
* Reduce over-reliance on print debugging
* Improve code-review to catch fresh bugs early.

Details and references: tzanko.substack.com/p/what-constitutes-debugging?utm_source=bsky&utm_medium=social&utm_campaign=debugging_launch

State inspection: 70% of the time it's done using logs/print statements and only 30% of the time via debuggers

What devs actually do with their time during debugging:
* Editing code: 41%
* Run/test: 29% (and 84% of testing is manual)
* Inspect state (logs, breakpoints): 16% (only 40% of episodes)
* Navigate code: 15%
* Consult resources: 6%

Fresh bugs (those appearing during ongoing work) take 3 minutes to fix on average. But committed bugs (those appearing in the issue tracker) take 29 minutes on average.

Debugging eats a lot of time: studies show between 35%-50% of dev time is spent debugging