On 2006 June 15 12:28, tim Rowledge wrote:
>
> Comments that explain the intent, the purpose, the reason, for the
> code are crucial to maintaining a system. 

+1

> The old joke "comments? why 
> do think it's called code?" sums up the antithesis of responsible
> programming that seems to be the normal approach. Yes, reading the
> code tells you what it *does* do (until you find a compiler bug for
> example) but it tells you nothing about what it was intended to do,
> what spec it was putatively meeting or what limits on its
> functionality were known about.

+1

>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Strange OpCodes: SD: Self Destruct