title: "Redundant" javadoc - desirable in public-facing APIs?
body: <p>When you see something like this:</p>
  
  <pre><code>/**
  * Gets the Person's identifier.
  *
  * @return The person identifier.
  */
  public long getId()
  </code></pre>
  
  <p>a lot of you may think "what's the point of repeating what the code implies"? I personally agree, and would not bother with writing such a comment if my code was only seen and used by people in my company.</p>
  
  <p>If however I was writing, say, an Apache Commons library I think it could be argued that it enhances the consuming programmer's experience. Seeing accessible methods with empty space in the javadoc just creates a feeling of a lack of friendliness/maturity/support to a consumer that can affect their confidence in your api and ultimately choose a competitor.</p>
  
  <p>Is there a difference in desirability of redundant javadoc for public-facing versus non-public-facing APIs?</p>