<p>How many can relate do this?</p>

<blockquote>
  <h1>Server Error in / Application</h1>
  
  <hr>
  
  <h2><em>Object reference not set to an object</em></h2>
  
  <p><strong>Description:</strong> Object reference not set to an object.</p>
  
  <p><strong>Exception Details:</strong> <code>System.NullReferenceException</code>: Object reference not set to an object.</p>
  
  <p><strong>Source Error:</strong></p>

<pre><code>Line 56:    posts.Add(post);
</code></pre>
</blockquote>

<p>On a more serious note, what are the first things you look for when you see the
yellow screen of death? Half the time the debug trace isn't actually telling you what the problem is (understandable I guess).</p>

<p>I must admit, I still use <code>Response.Write</code> more than I should.  I just get lazy going through the debugger.  What techniques do you use to debug the problem?</p>

If I'm unable to identify/resolve the issue using the error message that the page presents to me, I will typically try to use the Windows Event Viewer to help me identify what is causing the issue.
For example, SharePoint errors are sometimes far less than descriptive.  So, I'll combine what I'm seeing on the Y.S.O.D. with error messages from the Event Viewer to help me narrow down the cause.
I will do my best to ask a co-worker or other associate that I think might have some experience that might help.  If I'm still unable to identify the cause, I will resort to Google armed with all the information.