The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] The Elements of Programming Style (book) - was Re: Discuss of style and design of computer programs
Date: Sat, 6 May 2017 10:16:03 -0400	[thread overview]
Message-ID: <f3bc4461-5a08-b227-2868-eb4aeb247289@telegraphics.com.au> (raw)
In-Reply-To: <5a2d6cc957c2efcd968f35aa5557c7a0e309dd27@webmail.yaccman.com>

On 2017-05-06 1:33 AM, Steve Johnson wrote:
> In 1973, I spent 9 months at the University of Waterloo, home of Watfor.
>   I taught a course in "Advanced Application Techniques" -- the language
> was FORTRAN, and the techniques included such things as using libraries
> and handling errors in input data...
> ...
> in fairness, I didn't (and don't) know any better way to learn style
> than doing a lot of reading, a lot of writing, and getting criticized
> constructively by those with more experience.  For me, a lot of what I
> learned was from Stan Brown at the Labs, who read piles of my
> (atrocious) FORTRAN code and repeatedly pointed out that when you wrote
> a program, you were not just communicating with the computer, but also
> other humans (including yourself) who would read (and perhaps modify)
> the code in the future...

As a longtime maintenance programmer: I could not agree more. Thankfully 
this idea is fairly well accepted today. Although, I am working on a 
project right now that makes me think the author simply never considered 
that anyone else might ever read or maintain it.

In this context, one of the timeless classics is The Elements of 
Programming Style (Kernighan and Plauger). It had a huge effect on my C 
when I read it years ago and I still try to apply its lessons every day 
in any language.

--Toby


>
> Steve
>
>
>
>     ----- Original Message -----
>     From:
>     "Doug McIlroy" <doug at cs.dartmouth.edu>
>
>     To:
>     <lm at mcvoy.com>, <doug at cs.dartmouth.edu>, <clemc at ccc.com>
>     Cc:
>     <tuhs at minnie.tuhs.org>
>     Sent:
>     Fri, 05 May 2017 22:02:21 -0400
>     Subject:
>     Re: [TUHS] Discuss of style and design of computer programs from a
>     user stand point [was dmr note on BSD's sins]
>
>
>     Clem wrote, "So, I wonder do any of the schools like Darthmouth and
>     the like
>     teach courses that study 'style' and taste in CS."
>
>     Some time around 1970, Bob Rosen instituted a program-reading
>     course at the University of Iowa, by overt analogy to the
>     study of literature. Style was certainly a central concern;
>     I'm not sure about the deeper matter of taste. I'm not aware
>     of other examples, except perhaps for a collaboration between
>     Don Kunth and a teachaer of (I think) creative writing--a
>     course whose content I can't recall.
>
>     Doug
>



      parent reply	other threads:[~2017-05-06 14:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 15:20 [TUHS] Discuss of style and design of computer programs from a user stand point [was dmr note on BSD's sins] Clem Cole
2017-05-05 15:37 ` Bakul Shah
2017-05-06  2:16   ` Noel Hunt
2017-05-06  2:40     ` Toby Thain
2017-05-06  6:07     ` Bakul Shah
2017-05-06 22:11       ` Steve Johnson
2017-05-06 23:35         ` Larry McVoy
2017-05-07  4:06       ` Dan Cross
2017-05-07 13:49         ` [TUHS] Discuss of style and design of computer programs from a user stand point Michael Kjörling
2017-05-06  2:02 ` [TUHS] Discuss of style and design of computer programs from a user stand point [was dmr note on BSD's sins] Doug McIlroy
2017-05-06  5:33   ` Steve Johnson
2017-05-06  9:18     ` [TUHS] Discuss of style and design of computer programs from a user stand point Michael Kjörling
2017-05-06 13:09       ` Nemo
2017-05-06 13:44         ` Michael Kjörling
2017-05-06 14:40       ` Larry McVoy
2017-05-06 15:09         ` [TUHS] Discuss of style and design of computer programs from a Corey Lindsly
2017-05-06 15:20           ` Michael Kjörling
2017-05-06 15:24             ` Larry McVoy
2017-05-06 15:51               ` Michael Kjörling
2017-05-06 15:53                 ` Larry McVoy
2017-05-06 20:00             ` Steve Nickolas
2017-05-06 21:45               ` Michael Kjörling
2017-05-07  7:42                 ` Stephen Kitt
2017-05-06 15:23           ` ron minnich
2017-05-06 15:44             ` Michael Kjörling
2017-05-06 18:43         ` [TUHS] Discuss of style and design of computer programs from a user stand point Dave Horsfall
2017-05-06 19:50           ` Bakul Shah
2017-05-07  1:15             ` Warner Losh
2017-05-07  1:42               ` Noel Hunt
2017-05-07 13:54                 ` Michael Kjörling
2017-05-07 14:58                   ` arnold
2017-05-07 16:33                     ` Michael Kjörling
2017-05-07 15:13                 ` Warner Losh
2017-05-06 16:40       ` Kurt H Maier
2017-05-06 14:16     ` Toby Thain [this message]

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=f3bc4461-5a08-b227-2868-eb4aeb247289@telegraphics.com.au \
    --to=toby@telegraphics.com.au \
    /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).