title: The field must have a documentation header - Style Cop - Code smell?
body: <p>I was just running style cop against some of my code and got a few:</p>
  
  <pre><code>SA1600: The field must have a documentation header.
  </code></pre>
  
  <p>Now don't get me wrong I like style cop, it's great when you work on a project with more then one person but this rule seems a bit excessive to me.  Why would you want to add:</p>
  
  <pre><code>    /// &lt;summary&gt;
      /// blah blah blah
      /// &lt;/summary&gt;
  </code></pre>
  
  <p>to the top of every variable.  I'm pretty sure that I remember someone saying(Martin Fowler, Kent Beck..can't really remember ATM) that comment should say "why" not "what" and I really can't see how you can explain why on a variable. </p>
  
  <p>I also find code that has comments on every variable harder to read because all you see is fluff.</p>
  
  <p>My thoughts are if you have to explain what every variable is then you are really failing in terms of naming.</p>
  
  <p>Does anyone else find commenting variables a bit of a code smell or is it just me.</p>