The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] really Pottering vs UNIX
Date: Thu, 14 Sep 2017 16:46:07 -0400	[thread overview]
Message-ID: <CAC20D2M9E0TdK-wnLjMDbDF+qfnWgJCEikBq0RmrT9=oFSGEuQ@mail.gmail.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]

On Thu, Sep 14, 2017 at 4:09 PM, Jon Steinhart <jon at fourwinds.com> wrote:

>
> Well, I'd suggest that a lot of this has to do with people who have vision
> and people who don't.  When you look at UNIX, you see something created by
> a bunch of very talented people who had a reasonably shared vision of what
> they were trying to achieve.
>

​Jon - I mostly agree, but would twist it a little differently (hey, we've
been arguing since the 1970s, so why stop now).

I think you are actually touching on an idea that has been around humanity
for a long time that is independent of the computer field.  We call it
"good taste."  Part of acquiring good taste is learning what is in bad
taste, a heavy dose of experience and frankly the ability to evaluate your
own flaws.   What I always love about Dennis, Ken, Doug, Steve and the rest
if the team is their willingness to accept the shortcomings and compromises
that were made as the developed UNIX as a system.   I never saw them trying
to claim perfection or completeness, much less and end state had been
reached.  Always looking for something better, more interesting.  And
always, standing on the shoulders of others...

What I really dislike about much of the crowd that has been discussed is
that they often seem more contented to kick people in the shins that
standing on their shoulders.

I used to say, when we were hiring people for some of my start-ups, what we
wanted was experienced folks that had demonstrated good taste.  Those are
people you can trust; and will get you pretty close to where you want to be.

In fact, to pick on one of my previous employers, I have always said, what
DEC got wrong, was it was always striving to be perfect.  And lots of
things never shipped, or when they did (like Alpha) it was wonderful, but
it did not matter.  The opportunity window had passed.

Part of "good taste" is getting the job done and on time.  Being "good
enough" and moving on to the next thing.   Sun (certainly at the beginning)
was pretty good at this idea.   The UNIX team clearly got a lot of it right.

It is easy to throw stones at others.  It is hard to repeatedly get so much
right for so long and UNIX has and did.

Clem

​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170914/da3bc291/attachment.html>


             reply	other threads:[~2017-09-14 20:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 20:46 Clem Cole [this message]
2017-09-14 21:15 ` Bakul Shah
2017-09-15  1:24   ` Dan Cross
2017-09-15  1:39     ` Wesley Parish
2017-09-15  3:00     ` Kurt H Maier
2017-09-15  5:42     ` Steve Johnson
2017-09-15 13:26       ` Clem Cole
2017-09-15 19:10       ` Chris Torek
2017-09-15 19:19         ` Paul Winalski
2017-09-16 18:05         ` [TUHS] How do we learn about maintainability - was " Toby Thain
2017-09-16 19:12           ` [TUHS] Maintainability, Guilds, RMS, etc. all lumped into one Jon Steinhart
2017-09-17 18:50             ` Bakul Shah
2017-09-18 14:44           ` [TUHS] How do we learn about maintainability - was Re: really Pottering vs UNIX Clem Cole
2017-09-15  6:43     ` [TUHS] " Bakul Shah
     [not found] <mailman.1021.1505464341.3779.tuhs@minnie.tuhs.org>
2017-09-16 20:09 ` David
2017-09-18 14:17   ` Clem Cole
2017-09-18 14:23     ` David

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='CAC20D2M9E0TdK-wnLjMDbDF+qfnWgJCEikBq0RmrT9=oFSGEuQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).