>> Good code needs little javadocs. > > I disagree strongly. > > The Javadoc should present the public API (and should ideally be > written before the code - i.e. the code implements the docs). > > If the only documentation is the code, it is much harder for users to > determine how to use the API. > > For some code (interfaces, abstract methods) only Javadoc is available.
Did you even bother to read the blog post? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org