debugging strategy: use sounds or pictures

I'm still not super satisfied with the examples in this one, I'd love to hear examples of how you use visualizations or sounds to debug

@b0rk

Graphs - particularly multiple line graphs over time with a shared time bar so you can drag the bar on 1 graph & see what other values were on other graphs at the same time. Great for finding correlations.

Also flame graphs for finding slow/error causing components. Lightstep is a company that does this well.

@eswag @b0rk I had a slow running program once, so I fed it input of different sizes and got the time spent from various internal steps, then graphed the results. Seeing the shape of the graph (quadratic vs linear, etc) led me to where and what the problem was.