The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Hendrik Jan Thomassen <hjt@ATComputing.nl>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Any Good dmr Anecdotes?
Date: Wed, 18 Jul 2018 11:42:19 +0200	[thread overview]
Message-ID: <20180718094219.GA16388@vcursdoc.atcomputing.nl> (raw)

Several decades ago, Jim Joyce of San Francisco was one of the
more colorful chaps in the UNIX scene. Among other ventures he
had "The Independent UNIX Bookstore", and during Usenix conferences
he would rent a nearby hotel suite to sell his books to the
conference attendants. Jim once told me the following story (yes,
the topic is about dmr anecdotes).

One day a young man came to the hotel suite and asked, in a
somewhat exaggerated voice, "the best book to learn C programming".
Jim pointed at a gentleman in a nearby armchair, reading, and said:
"ask that gentleman because he knows everything there is to know
about C". So the young man approached said gentleman, and repeated
his question. The answer he got was: "Sorry, I can't help you, 
because I never had to learn C". Which left the young man flabbergasted.


-- 
Hendrik-Jan Thomassen     <hjt@ATComputing.nl>
AT Computing              Linux opleiders & consultants
Kerkenbos 1238            Tel +31 24 352 72 82
6546 BE  Nijmegen         www.atcomputing.nl

'If you think education is expensive, try ignorance.'


             reply	other threads:[~2018-07-18 10:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  9:42 Hendrik Jan Thomassen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-03  7:27 arnold
2018-07-02 19:55 Paul Ruizendaal
2018-07-01 16:35 Norman Wilson
2018-06-30  1:31 Larry McVoy
2018-06-30  1:45 ` Jon Forrest
2018-06-30 18:43   ` Steve Johnson
2018-06-29  7:53 Warren Toomey
2018-06-29 10:53 ` ches@Cheswick.com
2018-06-29 12:51   ` John P. Linderman
2018-06-30  0:50   ` Steve Johnson
2018-06-30 11:44     ` Arrigo Triulzi
2018-06-30 22:42       ` Arthur Krewat
2018-06-30 23:29         ` Arrigo Triulzi
2018-07-01  4:17           ` Larry McVoy
2018-07-01 11:42           ` ron
2018-07-01  5:29       ` Dave Horsfall
2018-07-01  8:28         ` Arrigo Triulzi
2018-07-01 11:34         ` ron
2018-07-09 16:30           ` Random832
2018-07-09 17:13             ` Clem Cole
2018-07-10  5:54               ` arnold
2018-07-10  6:09                 ` George Michaelson
2018-07-10  7:19                   ` arnold
2018-07-11  0:20                     ` Noel Hunt
2018-07-11  1:31                       ` Larry McVoy
2018-07-11  1:37                         ` George Michaelson
2018-07-11  1:37                         ` ron minnich
2018-07-11  3:12                           ` Larry McVoy
2018-07-13  9:08                       ` ches@Cheswick.com
2018-07-13 14:10                         ` ron
2018-07-10 14:10                 ` Clem Cole
2018-07-03 17:34       ` Perry E. Metzger
2018-06-29 23:55 ` Dave Horsfall
2018-06-30  0:06   ` Greg 'groggy' Lehey
2018-06-30 14:20   ` John P. Linderman

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=20180718094219.GA16388@vcursdoc.atcomputing.nl \
    --to=hjt@atcomputing.nl \
    --cc=tuhs@minnie.tuhs.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).