Back to “how not to” series.

Today I found a more or less funny article about this topic.

I think that most of us Java developers have spent tons of hours reading badly written javadocs (in the lucky case), and we can tell long stories about these memories.
Even if you consider yourself an experienced developer sometimes you can fall into a trap put by an outdated javadoc comment.

I personally have developed an interesting habit: don’t read javadoc only if it is longer than the autogenerated joavadoc, and instead use JadClipse and decompile the code. It kind of spared me a lot of time. In Eclipse it is very easy to have a class decompiled, so don’t need to leave the IDE, but for those developing in other environment this is also possible using external tools like Front End Plus and others.

One thing is true: badly written code is even worse in a decompiled format, but most of the time for me it was even educative to see different coding approaches.

So my advice, ignore the Javadoc reading in case of too short text and go directly to decompiling of the code.

Read the whole article at http://java.dzone.com/news/how-not-write-java

Happy coding

N