The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] DEC and Dave Cutler (was Re: The John Snow's of the UNIX family)
Date: Wed, 16 Jan 2019 11:55:03 -0500	[thread overview]
Message-ID: <CABH=_VQ+pgdSTykpPN8WzViMvkektq6aZaNTr-HkC4fG=Cty=g@mail.gmail.com> (raw)

On 1/16/19, Kevin Bowling <kevin.bowling@kev009.com> wrote:
> I’ve heard and personally seen a lot of technical arrogance and
> incompetence out of the Masshole area.  Was DEC inflicted?  In
> “Showstopper” Cutler fled to the west coast to get away from this kind of
> thing.
>
Having worked at DEC from February 1980 until after the Compaq
takeover, I would say that DEC may have exhibited technical arrogance
from time to time, but certainly never technical incompetence.  DEC's
downfall was a total lack of skill at marketing.  Ken Olsen believed
firmly in a "build it and they will come" philosophy.  Contrast this
with AT&T's brilliant "Unix - consider it a standard" ad campaign.

DEC also suffered from organizational paralysis.  KO believed in
decisions by consensus.  This is fine if you can reach a consensus,
but if you can't it leads to perpetually revisiting decisions and to
obstructionist behavior.  There was a saying in DEC engineering that
any decision worth making was worth making 10 times.  As opposed to
the "lead, follow, or get out of the way" philosophy at Sun.  Or
Intel's concept of disagree and commit.  DEC did move towards a
"designated responsible individual" approach where a single person got
to make the ultimate decision, but the old consensus approach never
really died.

Dave Cutler was the epitome of arrogance.  On the technical side, he
got away with it because his way (which he considered to be the only
way) was usually at least good enough for Version 1, if not the best
design.  Cutler excelled in getting V1 of something out the door.  He
never stayed around for V2 of anything.  He had a tendency to leave
messes behind him.  A Cutler product reminded me of the intro to "The
Peabodys" segment of Rocky & Bullwinkle.  A big elaborate procession,
followed by someone cleaning up the mess with a broom.

Cutler believed in a "my way or the highway" approach to software
design.  His move to the west coast was to place himself far enough
away that those who wanted to revisit all his decisions would have a
tough time doing so.

On the personal side, he went out of his way to be nasty to people, as
pointed out elsewhere in this thread.  Although he was admired
technically, nobody liked him.

-Paul W.

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 16:55 Paul Winalski [this message]
2019-01-16 17:14 ` Clem Cole
2019-01-16 17:33   ` Larry McVoy
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='CABH=_VQ+pgdSTykpPN8WzViMvkektq6aZaNTr-HkC4fG=Cty=g@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=kevin.bowling@kev009.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).