On 18 August 2012 14:34, Fabrizio Giudici <[email protected]> wrote: > > Also, there's a thing to clarify. "Unnecessary" means "zero" and I'd give a > very different response if we're talking about "zero comments" or "a few > comments". >
You're right - "almost completely unnecessary" is what I was going for. I can think of cases where there's no natural way to express something in code, and a comment is the most sensible form. One example that springs to mind is using Javadoc in a Java test file to say "some of this feature is implemented on the client side, in JavaScript, the tests are in file x". I've very much been in the "whitebox" situation I described previously. Also there is a bunch of other practices which support almost-zero-comments (TDD, acceptance testing, pair programming, whiteboarding). Which is why I've tried to be careful to say that circumstances matter. (I'm just a little sensitive to the "if it works for you it's because you're doing something trivial" argument) Cheers, Graham -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
