CodeTracer (@CodeTracerIDE) profile picture
Joined May 2025
Photo by CodeTracer (@CodeTracerIDE)
What does this mean for you and your team? * Invest in debugging tools and training * Reduce over-reliance on print debugging * Implement rigorous code-review to catch fresh bugs before they become committed. Details and references: tzanko.substack.com/p/what-c…
1
2
176
State inspection: 70% of the time it's done using logs/print statements and only 30% of the time via debuggers
1
1
1
169
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%
1
1
1
83
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.
1
1
1
90
The effort is not evenly distributed: 79% of debugging time goes to the hardest 26% of bugs
1
1
1
106
Debugging eats a lot of time: studies show between 35%-50% of dev time is spent debugging
1
1
1
117
What constitutes debugging? Research on 30h of live-coding streams shows how developers spend their time during debugging episodes. Here are some of the insights of the research. Full post: tzanko.substack.com/p/what-c…
2
6
2
18
6,017
What constitutes debugging? Research on 30h of live-coding streams shows what devs actually do during debugging episodes. Full post: tzanko.substack.com/p/what-c…
1
86
[1/4] @blocksense_ and @MetacraftLabs have teamed up to create the future of smart contract and ZK circuit debugging, earning us more than 1000 GitHub stars in 2 weeks. With @NoirLang support already shipped and Stylus and Move in the works, what should we target next?
61
55
3
128
3,308