Q:

commenting code

whats the most professional and informative way of commenting code. Are there any standards out there? 
p.s. it doesn't have to be javadoc, just info on what to include - any common layouts etc
cheers guys

A:

There's a big difference between commenting internal method code and commenting APIs.
For code, I'm not familiar of specific practices or layouts. "Use common sense" is the best one. Don't document anything that is obvious from the code, etc, but document everything that is not immediately clear. And remember, the one thing worse than code without comments is code with outdated comments. More comments mean more stuff that needs to be updated.
For API documentation, there are two approaches. The document-everything-in-tons-of-details (proposed by Sun), and the more agile (propose the important parts only). In many places, you are not expected to document API stuff that is obvious from the signature. 
While a complete documentation of the method (the sun approach) is important to have a well fleshed up spec, my research shows that it makes it more difficult to spot important caveats, likely leading to more errors. 
For APIs, see also: Creating Great API Documentation: Tools and Techniques

