title: Standard methods of debugging
body: <p>What's your standard way of debugging a problem? This might seem like a pretty broad question with some of you replying 'It depends on the problem' but I think a lot of us debug by instinct and haven't actually tried wording our process. That's why we say 'it depends'.</p>
  
  <p>I was sort of forced to word my process recently because a few developers and I were working an the same problem and we were debugging it in totally different ways. I wanted them to understand what I was trying to do and vice versa.</p>
  
  <p>After some reflection I realized that my way of debugging is actually quite monotonous. I'll first try to be able to reliably replicate the problem (especially on my local machine). Then through a series of elimination (and this is where I think it's problem dependent) try to identify the problem.</p>
  
  <p>The other guys were trying to do it in a totally different way.</p>
  
  <p>So, just wondering what has been working for you guys out there? And what would you say your process is for debugging if you had to formalize it in words?</p>
  
  <p>BTW, we still haven't found out our problem =)</p>