The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: david@kdbarto.org (David)
Subject: [TUHS]  daemons are not to be exorcised/Comments in code
Date: Thu, 22 Mar 2018 12:01:40 -0700	[thread overview]
Message-ID: <C4983039-5958-4336-ADFE-9A20DA9767B7@kdbarto.org> (raw)
In-Reply-To: <mailman.68.1521732132.3788.tuhs@minnie.tuhs.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]


> From: Dave Horsfall <dave at horsfall.org>
> Yep, and I'm glad that I had bosses to whom I didn't have to explain why 
> my comments were so voluminous.
> 
> And who first said "Write your code as though the next person to maintain 
> it is a psychotic axe-wielding murderer who knows where you live"?  I've 
> often thought that way (as the murderer I mean, not the murderee).
> 
> I'd name names, but he might be on this list...
> 
I’ve always said that the person was a ‘reformed’ axe-wielding murderer
who knows where you live.

Please, a little decorum.

W.R.T. comments in code, and a bit of Unix, when I taught Unix Systems
programming at UCSD one of my students wanted to use his personal
computer for the programming. I didn’t care as long as it would pass the
tests I ran after the fact.

After his second homework was turned in, I stopped looking at his code
or even running it, as the comment blocks were just so well done. Nary
a comment in the function itself, just a block before each one very clearly
explaining what was happening.

	David



           reply	other threads:[~2018-03-22 19:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.68.1521732132.3788.tuhs@minnie.tuhs.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C4983039-5958-4336-ADFE-9A20DA9767B7@kdbarto.org \
    --to=david@kdbarto.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).