The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Donner <marc.donner@gmail.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Fred Brooks died
Date: Mon, 28 Nov 2022 06:39:48 -0500	[thread overview]
Message-ID: <CALQ0xCA17wkjsjhrvTPq=ukvKsBesBrcZ1s=pDE0casHhBV2vg@mail.gmail.com> (raw)
In-Reply-To: <202211272100.2ARL00ua032601@freefriends.org>

[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]

In 1980 I applied to grad schools, including UNC.  I had read "The Mythical
Man-Month" by then, so I was floored one day sitting in my office when the
phone rang and I heard, "This is Fred Brooks."  I visited UNC where I saw
the famous row of clocks that Steve Bellovin mentions in his memorial
post.  The "System 360 Principles of Operation" remains one of the most
important pieces of writing in computer history, in my opinion, because it
dominated the hardware and established the principle that an architecture
ensures software execution.
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>


On Sun, Nov 27, 2022 at 4:00 PM <arnold@skeeve.com> wrote:

> I found two typos in the 25th anniversary edition of the book. I used
> finger to find his postal address and sent him a letter. He replied with
> a nice thank you email. One of them had been in the book since it was
> first published!
>
>
> Clem Cole <clemc@ccc.com> wrote:
>
> > He was a Unix (and UUCP) fan and also an early Masscomp customer.  Let's
> > say I was a tad in awe when I was answering his questions when he came on
> > a factory visit.  But he was cool when I asked him if I could go back to
> my
> > office and get his book so he could sign it.  I think he was pleased to
> see
> > a then young professional have it in his office.
> > ᐧ
> >
> > On Sun, Nov 27, 2022 at 3:19 PM Dave Horsfall <dave@horsfall.org> wrote:
> >
> > > On Sun, 27 Nov 2022, John P. Linderman wrote:
> > >
> > > > We all probably read, and profited from, "The Mythical Man Month".
> > >
> > > Posted to COFF a week ago, as I didn't think that it was Unix-y...
> > >
> > > -- Dave
> > >
>

[-- Attachment #2: Type: text/html, Size: 2578 bytes --]

  reply	other threads:[~2022-11-28 11:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 12:10 [TUHS] " John P. Linderman
2022-11-27 13:46 ` [TUHS] " Ron Natalie
2022-11-27 20:19 ` Dave Horsfall
2022-11-27 20:52   ` Clem Cole
2022-11-27 21:00     ` arnold
2022-11-28 11:39       ` Marc Donner [this message]
2022-11-28 16:42         ` Adam Thornton
2022-11-27 20:32 Norman Wilson

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='CALQ0xCA17wkjsjhrvTPq=ukvKsBesBrcZ1s=pDE0casHhBV2vg@mail.gmail.com' \
    --to=marc.donner@gmail.com \
    --cc=arnold@skeeve.com \
    --cc=tuhs@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).