Optimize your debugging workflow with tapping_device
Have you ever examined your debugging process before? Do you know how efficient/inefficient your debugging strategy is? If the answers are “no”, this talk is for you.
In this talk, I will explain the way most of us debug programs, and why is it an O(log n) operation. And then, I will introduce a concept called “Object-Oriented Tracing” along with my tool: tapping_device. By adopting the concept and with the help of my tool, I’ve been able to make debugging an O(1) operation. Here’s an example that I used this strategy to debug a Rails issue.
Of course, I’m not saying I’ve found a silver bullet for debugging, so I will also show you its limitation and where it suits best.