On Wed, 01 May 2013 10:57:01 +0200, Roland Tepp <[email protected]> wrote:
This is so far the best and the most concise comment in favor of code
comments I've read so far.
Thanks man.
The problem is: redundant comments, in my experience, tends to be always
out of sync with the code after some time. At that point, what's the right
one? The code or comments? :-) If you're testing at a decent level, it's
the code. Thus, what's that redundancy for?
teisipäev, 30. aprill 2013 21:16.39 UTC+3 kirjutas Vince O'Sullivan:
On Monday, 15 April 2013 07:38:03 UTC+1, brucechapman wrote:
If what we write first is "the simplist thing that might work", then
I'd suggest comments should explain code that is not apparently the
"the
simplist thing that might work". or "comments should explain why the
simplistic thing that might have worked, didn't"
--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - [email protected]
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/javaposse?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
