On Thu, May 26, 2011 at 8:07 PM, Steven D'Aprano
wrote:
> Another use for comments is to explain *why* rather than *what*. No
> matter how readable your code is, if you don't understand why it is done,
> you can't effectively maintain it. If the why is obvious, you don't need
> a comment.
That's
On Thu, 26 May 2011 14:06:56 +1000, Chris Angelico wrote:
> On Thu, May 26, 2011 at 10:58 AM, Richard Parker
> wrote:
>> It's time to stop having flame wars about languages and embrace
>> programmers who care enough about possible future readers of their code
>> to thoroughly comment it. Comments
On Thu, May 26, 2011 at 10:58 AM, Richard Parker
wrote:
> It's time to stop having flame wars about languages and embrace programmers
> who care enough about possible future readers of their code to thoroughly
> comment it. Comments are far more valuable than the actual language in which
> the cod
> Writing code is primarily for *human readers*. Once you've compiled the
> code once, the computer never need look at it again, but human being come
> back to read it over and over again, to learn from it, or for
> maintenance. We rightfully value our own time and convenience as more
> valuab
