title: Is it bad form to exclude godocs on exported names?
body: <p>According to "Effective Go" <a href="https://golang.org/doc/effective_go.html#commentary" rel="noreferrer">golang.org/doc/effective_go</a></p>
  
  <blockquote>
    <p>Every exported (capitalized) name in a program should have a doc comment.</p>
  </blockquote>
  
  <p>Let's say I have a view handler on a simple web application</p>
  
  <pre><code>// Handle the front page of the website
  func FrontPageView(w http.ResponseWriter, r *http.Request) {
      controllers.RenderBasicPage(w, "frontPage") 
  }
  </code></pre>
  
  <p>My question is this: is that godoc <em>really</em> necessary? Perhaps I'm just in love with Robert Martin's Clean Code right now, but it seems an effectively named variable, in this case <code>FrontPageView</code> removes the need for such a godoc. This is probably a derivative/duplicate of "are javadocs necessary?" or "are python docstrings necessary?", but I do want to make sure that when learning a new language I'm sticking to the language-specific canonical ways-to-do-things. </p>