This link has been bookmarked by 27 people . It was first bookmarked on 26 Jul 2008, by Mr. DiGi.
-
17 May 09
-
08 May 09
-
13 Dec 08
-
16 Oct 08
Cristián RomoComments can be excessive and unnecessary when the same code written a different way - perhaps renamed variables or encasement in a descriptive function - can be self explanitory.
-
23 Aug 08
-
08 Aug 08
-
31 Jul 08
-
30 Jul 08
-
29 Jul 08
-
28 Jul 08
-
As Sammy Larbi said in Common Excuses Used To Comment Code, if your feel your code is too complex to understand without comments, your code is probably just bad. Rewrite it until it doesn't need comments any more. If, at the end of that effort, you still feel comments are necessary, then by all means, add comments. Carefully.
-
-
-
ou should always write your code as if comments didn't exist. This forces you to write your code in the simplest, plainest, most self-documenting way you can humanly come up with.
-
if your feel your code is too complex to understand without comments, your code is probably just bad. Rewrite it until it doesn't need comments any more.
-
-
27 Jul 08
bob dolanThe code already tells us how it works; we need the comments to tell us why it works. You should always write your code as if comments didn't exist. This forces you to write your code in the simplest, plainest, most self-documenting way you can humanly co
-
-
You should always write your code as if comments didn't exist.
-
[advertisement] Peer Code Review. No meetings. No busy-work. Customizable workflows and reports. Try Jolt Award-winning Code Collaborator.
-
-
26 Jul 08
-
25 Jul 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.