It's off-topic, but I think for programmers this may be sort of interesting discussion. Lets start with a few questions: What do you think it's a good practice for documenting your code? What does it means to have self-documenting code? There are people who believes using absolutely english like phrases for variable/function names, even if it means it'll be really long. I've seen people coding with elaborously long names. However, I'd say they don't really get what self-documenting code really is all about. Self-documenting code is clean with adequate documentation, and easy to follow. With long names like that, it clutters the view; it's error prone; it slows down development process. The same can be said to long documentations. so what would you prefer long names or long documentations, or something in between? =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets