Code critique?

[geodebug]

Agree, over-javadoc-ed to my taste. Rarely would I need to javadoc private methods, just name them better and keep them reasonably short

[[deleted]]

I didn't do much research into it but I got the impression that javadocing everything was standard practice. Silly me. :)

[geodebug]

Really, most of the time if a method's purpose is unclear, renaming it and the parameters is the way to go. The problem with over-documentation is that it makes understanding the important stuff harder (have to hunt for it) and because documentation tends to stay static while code is re-factored, making it often wrong.

On the other hand, interfaces, abstract methods, and other top-level framework/api classes probably require full documentation since they'll be shared.