9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Laura Creighton <lac@cd.chalmers.se>
To: 9fans@cse.psu.edu
Cc: lac@cd.chalmers.se
Subject: Re: [9fans] Simple
Date: Thu, 23 Nov 2000 23:09:18 +0100	[thread overview]
Message-ID: <200011232209.XAA16138@boris.cd.chalmers.se> (raw)


>simple?  that's hard.  you either understand it or you don't.
>boyd

No.  It *is* teachable.  You have to hold somebody's feet to the fire
and, line by line, say ``what does that piece of code do.  Now. Is that
something that we need to do.  And is that something we need to be doing
*here*.''  But the only reason I know how to do it is because a long
time ago Geoff Collyer and Henry Spencer (hi Geoff! thank you by the way)
held *my* feet to the fire and did the same thing.  A surprising amount of
bad code is in programs because the person who wrote it does not know
what the code does, and does not want to admit ignorance, even to themselves.
This is programming by sympathetic magic.  These charms and those chants
somehow made that code work over there, so I had better put some charms and
chants in my code as well.

I have spent a good part of today trying to understand why boyd's e acute
came to me as an e and not as an i.  After wading around in MIME doc for
a while I have much more sympathy for the sympathetic magic approach. I
could understand this stuff, but boy oh boy the temptation to try to get
away with using it without understanding it is enormous.



             reply	other threads:[~2000-11-23 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-23 22:09 Laura Creighton [this message]
2000-11-23 22:32 ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2000-12-03  0:40 kim kubik
2000-11-23 22:08 nigel
2000-11-27  9:40 ` Douglas A. Gwyn
2000-11-23 21:44 Laura Creighton
2000-11-23 21:52 ` Boyd Roberts

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=200011232209.XAA16138@boris.cd.chalmers.se \
    --to=lac@cd.chalmers.se \
    --cc=9fans@cse.psu.edu \
    /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).