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…
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.
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…
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
CodeTracer is designed to eventually support any programming language!
At @balkanruby, we presented our #Ruby build:
youtube.com/watch?v=PkvZxHv9…
135
CodeTracer retweeted
[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?

