From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,f3bebae566a54cab X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!news-out.readnews.com!news-xxxfer.readnews.com!panix!newsfeed-00.mathworks.com!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Some exciting new trends in concurrency and software design Date: Wed, 29 Jun 2011 17:39:05 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <8a5765ba-622a-42cd-9886-28ed7cfed31e@s17g2000yqs.googlegroups.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls6.std.com 1309383545 10234 192.74.137.71 (29 Jun 2011 21:39:05 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Wed, 29 Jun 2011 21:39:05 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:vkgxkqsst6wRHwrZWHBd886HyvQ= Xref: g2news2.google.com comp.lang.ada:21031 Date: 2011-06-29T17:39:05-04:00 List-Id: anon@att.net writes: > Taking a weekend break may clear your head that may help solve the > problem but it can also cause you to forget how you were solving that > problem. > > Plus, back in the day, some of the profs would say "It might be the best > code in the world, but without comments its a grade of zero." Because > even the prof may not remember which problem your working on. Yes, indeed! I find it extremely annoying when I have to read an entire screenful of code in order to puzzle out what this code is trying to accomplish, when a little comment would explain it. > And it only take a few comments. Under-commenting is far worse than over-commenting. You shouldn't comment the obvious. But the person writing the code is necessarily a poor judge of what's obvious -- that person just got done thinking carefully about it, so it all seems obvious, but it's mysterious to somebody else (or to the same person a week later). So I say: err on the side of too many comments. - Bob