Linked by Jesse Smith on Wed 14th Apr 2010 21:00 UTC
Thread beginning with comment 419072
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: I will risk it
by StephenBeDoper on Thu 15th Apr 2010 19:47
in reply to "RE[2]: I will risk it"
I'll pick properly coupled code with good descriptive variable names over the average javadocced code anyday.
Javadoc describes your attributes, which is a good thing if you are coding an api. But to use it to make somebody understand your code it's useless. it does not describe the structure and logic behind your classes.
I've seen too many getFoo() functions with the the javadoc comment "gets foo". Try to pick you variable, class and method names so they don't need any javadoc.





Member since:
2009-08-18
I got bolloxed at work for "wasting time" writing Javadocs today ... I kid you not.