title: What is your personal approach/take on commenting?
body: <h3>Duplicate</h3>
  <blockquote>
  <p><a href="https://stackoverflow.com/questions/142830/what-are-your-hard-rules-about-commenting-your-code">What are your hard rules about commenting?</a></p>
  </blockquote>
  <p>A Developer I work with had some things to say about commenting that were interesting to me (see below). What is your personal approach/take on commenting?</p>
  <blockquote>
  <p>&quot;I don't add    comments to code unless
  its a simple heading or there's a<br />
  platform-bug or a necessary
  work-around that isn't obvious. Code
  can    change and comments may become
  misleading. Code should be<br />
  self-documenting in its use of
  descriptive names and its logical<br />
  organization - and its solutions
  should be the cleanest/simplest way<br />
  to perform a given task. If a
  programmer can't tell what a program<br />
  does by only reading the code, then
  he's not ready to alter it.<br />
  Commenting tends to be a crutch for
  writing something complex or<br />
  non-obvious - my goal is to always
  write clean and simple code.&quot;</p>
  <p>&quot;I think there a few camps when it
  comes to commenting, the
  enterprisey-type who think they're
  writing an API and some grand
  code-library that will be used for
  generations to come, the
  craftsman-like programmer that thinks
  code says what it does clearer than a
  comment could, and novices that write
  verbose/unclear code so as to need to
  leave notes to themselves as to why
  they did something.&quot;</p>
  </blockquote>