Generally the best comments are to describe "why" (sometimes "how") more than "what". Of course, good writers know their audience. If that code is somehow stra

Generally the best comments are to describe "why" (sometimes "how") more than "what". Of course, good writers know their audience. If that code is somehow strange in its organizational context, a few "what" comments and links to references, documentation, and/or tutorials can be great.