The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] DEC and Dave Cutler (was Re: The John Snow's of the UNIX family)
Date: Wed, 16 Jan 2019 09:33:41 -0800	[thread overview]
Message-ID: <20190116173341.GM7733@mcvoy.com> (raw)
In-Reply-To: <CAC20D2Oez96cn73tYLHRf39=M+ifv9e=_hcmUhwePf9O_NERNA@mail.gmail.com>

On Wed, Jan 16, 2019 at 12:14:30PM -0500, Clem Cole wrote:
> DC's magic was getting to the
> nut of the problem and getting what people cared about implemented quickly
> and out for users to try it.  The problem was his scheme, was that he was
> never part of the team that fixed it later.    I think I would have had
> more respect if he had quickly gotten the product out and then said, 'ok,
> we took these short cuts.  Let's fix them'  But as you pointed out, Dave
> never seems to see them as short cuts.  He was 'done.'

Ah, yes, the 1.0 person.  That's a nice gig if you can get it, but it is
rare that a company will put up with it.  The fact that DEC did sort of
indicates a broken engineering culture.

Sun, at least when I was there, would never put up with that.  If you
pushed something out the door you were expected to stick around and 
do the dot dot releases that fixed it before you got to move on to 
the next thing.  That was just part of the culture when I was there,
I sort of thought they over did it and people sort of polished the
turd forever.  I escaped that by focussing on performance, that let
me bounce all over the place, which was fun.

--lm

  reply	other threads:[~2019-01-16 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 16:55 Paul Winalski
2019-01-16 17:14 ` Clem Cole
2019-01-16 17:33   ` Larry McVoy [this message]
2019-01-16 17:29 ` Larry McVoy
2019-01-16 18:13   ` Clem Cole
2019-01-16 18:24     ` Larry McVoy
2019-01-16 18:32       ` Arthur Krewat
2019-02-02 14:34       ` Finn O'Leary
2019-02-02 21:22         ` Dave Horsfall
2019-02-03 19:57         ` Cág
2019-01-16 22:09   ` Theodore Y. Ts'o

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=20190116173341.GM7733@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=clemc@ccc.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).