If you configure the Eclipse Java compiler to issue warnings for missing Javadoc comments on non-overridden public members, it provides feedback that encourages one to minimize visibility declarations (e.g. favour private over package over protected over public visibility). It is easier to downgrade a member from public to package visibility then to write an inane comment.
... until the collector arrives ...
This "blog" is really just a scratchpad of mine. There is not much of general interest here. Most of the content is scribbled down "live" as I discover things I want to remember. I rarely go back to correct mistakes in older entries. You have been warned :)
