The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Charles H Sauer (he/him)" <>
Subject: [TUHS] Re: Managers/architects (was: AIX moved into maintainance mode)
Date: Thu, 19 Jan 2023 12:09:09 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Not trying to keep AIX in the discussion, but the 3 in 1 list should 
include Glenn Henry. Glenn was primarily a manager when I worked for 
him, but was an architect before then and is still a programmer -- see 
the summary at 


On 1/19/2023 12:00 PM, Marc Donner wrote:
> I'd certainly list Bob Sproull for all three, from personal observation.
> My guess is that Ivan Sutherland probably qualified back when he still 
> programmed ... I mean, after all, he invented the linked list in order 
> to implement his thesis program (Sketchpad) in about 1960.
> =====
> <>
> <>
> On Thu, Jan 19, 2023 at 12:50 PM Noel Chiappa < 
> <>> wrote:
>          > From: Larry McVoy < <>>
>          > At least 30 years ago I said "He's good programmer, a good
>     architect,
>          > and a good manager. I've never seen that in one person before".
>     Corby? Although he was just down the hall from me, I never saw him
>     operating
>     in any of those roles; maybe some of the old-time Unix people have some
>     insight. Saltzer is about off-scale in #2; probably good as a manager
>     (although I had a monumental blow-up with him in the hallway on the 5th
>     floor, but I was pretty close to unmanageable when I was young ;-);
>     he took
>     over Athena when it was stumbling, and got it going. Dave Clark is
>     high on
>     all three - he could manage me! :-)
>     Bob Taylor? PARC did some _incredibly_ important stuff in his time.
>     Yes, I
>     know a lot of the credit goes to those under him (Butler Lampson,
>     Alan Kay -
>     not sure if he was in Taylor's group, Boggs, Metcalfe, etc) but he
>     had to
>     manage them all. Not sure what his technical role was, though.
>     Vint Cerf? Again, A1*** as a manager, but had some failings as a
>     architect. I
>     think the biggest share of the blame for the decision to remove the
>     variable
>     size addresses from TCP/IP3, and replace them with 32-bit addresses in
>     TCP/IPv4, goes to him. (Alas, I was down the hall, not in the room,
>     that day;
>     I wasn't allowed in until the _next_ meeting. I like to think that
>     if I'd been
>     there, I could/would have pointed out the 'obvious' superior
>     alternative -
>     'only length 4 must be supported at this time'.)
>              Noel
>     PS: ISTR that about a month ago someone was asking for management papers
>     from that era (but I was too busy to reply); two good ones are:
>        - F. J.  Corbat??, C. T. Clingen, "A Managerial View of the
>     Multics System Development"
>     <>
>        - F. J. Corbat??, C. T. Clingen, and J. H. Saltzer, "Multics --
>     the first seven years"
> <>

voice: +1.512.784.7526       e-mail:
fax: +1.512.346.5240         Web:
Facebook/Google/Twitter: CharlesHSauer

  reply	other threads:[~2023-01-19 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 17:50 [TUHS] " Noel Chiappa
2023-01-19 18:00 ` [TUHS] " Marc Donner
2023-01-19 18:09   ` Charles H Sauer (he/him) [this message]
2023-01-20  3:47   ` John Cowan
2023-01-20 16:54     ` [TUHS] FYI: Apple Lisa [source Pascal code] goes “open source” Rich Morin
2023-01-20 17:07       ` [TUHS] " Ron Natalie
2023-01-19 21:12 ` [TUHS] Re: Managers/architects (was: AIX moved into maintainance mode) Lawrence Stewart
2023-01-19 21:30 Douglas McIlroy

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).