From: cym224@gmail.com (Nemo)
Subject: [TUHS] Discuss of style and design of computer programs from a user stand point
Date: Sat, 6 May 2017 09:09:27 -0400 [thread overview]
Message-ID: <CAJfiPzxKN09Y_8w7tPvAXjC=VZh-qJYpPezW40UV6B40K=5a5g@mail.gmail.com> (raw)
In-Reply-To: <20170506091857.GE12539@yeono.kjorling.se>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
On 06/05/2017, Michael Kjörling <michael at kjorling.se> wrote:
> I would actually take that one step further: When you are writing
> code, you are _first and foremost_ communicating with whatever human
> will need to read or modify the code later.
Something similar appears in the front of almost every Wirth book
(though sometimes honoured in the breach). That being said, there are
times when the code is transformed by optimization into something very
difficult to read. (We used noweb to document the transformation.)
N.
next prev parent reply other threads:[~2017-05-06 13:09 UTC|newest]
Thread overview: 36+ 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 [this message]
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 ` [TUHS] The Elements of Programming Style (book) - was Re: Discuss of style and design of computer programs Toby Thain
[not found] <mailman.821.1494062349.3779.tuhs@minnie.tuhs.org>
2017-05-06 17:52 ` [TUHS] Discuss of style and design of computer programs from a user stand point David
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='CAJfiPzxKN09Y_8w7tPvAXjC=VZh-qJYpPezW40UV6B40K=5a5g@mail.gmail.com' \
--to=cym224@gmail.com \
/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).