From: Larry McVoy <lm@mcvoy.com>
To: Richard Salz <rich.salz@gmail.com>, Larry McVoy <lm@mcvoy.com>,
tuhs@minnie.tuhs.org
Subject: Re: [TUHS] CMU Mach sources?
Date: Tue, 25 Jun 2019 19:56:46 -0700 [thread overview]
Message-ID: <20190626025646.GR925@mcvoy.com> (raw)
In-Reply-To: <20190626024503.GA43970@wopr>
On Tue, Jun 25, 2019 at 07:45:03PM -0700, Kurt H Maier wrote:
> On Mon, Jun 24, 2019 at 09:00:28PM -0400, Richard Salz wrote:
> > Is this really the kind of commentary appropriate for this list? I mean I'm
> > new here, but...
>
> It might not be, but it is definitely relevant to Unix. Arguably the
> drivers of Unix's development movement away from R&D-focused places and
> toward product-oriented entities had at least a little to do with
> Larry's topic of complaint. Product managers gained the ammunition to
> demand sustainable development practices, while R&D got a little leaner,
> a little more focused on demonstrating the thesis, a little less focused
> on who might need to run this code five years on...
In the good old days at Sun, we were very focussed on who would run
this code for decades to come. I think the engineers at Sun were very
focussed on helping people, the reason we were there was because the
work we did helped people. The leverage was how much work we could
do versus how much that helped people. That is product oriented.
I think the reason that any engineer works is because they feel like
their work helps someone. As an engineer, I wanted to go to the place
and do the work that had the best chance of helping someone. All of
Sun, when I was there, was like that. We were there to help. Yeah,
of course, we wanted to make money, but all of us wanted to help.
It's the dream, you do work, your work helps.
next prev parent reply other threads:[~2019-06-26 2:57 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 4:38 Chris Hanson
2019-06-23 5:15 ` Larry McVoy
2019-06-23 8:52 ` Andrew Warkentin
2019-06-23 13:39 ` Jon Forrest
2019-06-23 13:59 ` arnold
2019-06-23 14:03 ` Jason Stevens
2019-06-23 8:04 ` Jason Stevens
2019-06-23 14:54 ` Henry Bent
2019-06-23 21:52 ` Clem Cole
2019-06-25 0:06 ` Larry McVoy
2019-06-25 0:31 ` Theodore Ts'o
2019-06-25 0:45 ` Larry McVoy
2019-06-25 0:55 ` Kurt H Maier
2019-06-25 4:18 ` Larry McVoy
2019-06-26 23:19 ` [TUHS] Craft vs Research (Re: " Bakul Shah
2019-06-27 0:16 ` tuhs
2019-06-27 17:06 ` Clem Cole
2019-06-25 1:00 ` [TUHS] " Richard Salz
2019-06-25 8:00 ` Kevin Bowling
2019-06-25 12:11 ` Arthur Krewat
2019-06-25 12:17 ` Arthur Krewat
2019-06-26 2:45 ` Kurt H Maier
2019-06-26 2:56 ` Larry McVoy [this message]
2019-06-26 15:11 ` Theodore Ts'o
2019-06-26 17:44 ` Larry McVoy
2019-06-26 18:01 ` arnold
2019-06-26 18:18 ` Warner Losh
2019-06-26 19:22 ` Chris Hanson
2019-06-26 19:32 ` Ben Greenfield via TUHS
2019-06-26 20:21 ` Larry McVoy
2019-06-27 0:22 ` Chris Hanson
2019-06-27 1:02 ` Larry McVoy
2019-06-27 1:26 ` Chris Hanson
2019-06-27 4:01 ` Lyndon Nerenberg
2019-06-27 10:34 ` Ben Greenfield via TUHS
2019-06-27 10:59 ` arnold
2019-06-27 11:13 ` Ben Greenfield via TUHS
2019-06-27 11:39 ` arnold
2019-06-27 14:58 ` Warner Losh
2019-06-27 17:25 ` Larry McVoy
2019-06-26 19:30 ` Dennis Boone
2019-06-26 19:25 ` Adam Thornton
2019-06-23 8:27 ` Kevin Bowling
2019-06-25 3:07 ` Gregg Levine
2019-06-25 8:15 ` Kevin Bowling
2019-06-25 18:18 ` Chris Hanson
2019-06-25 20:23 ` Gregg Levine
2019-06-26 1:04 ` Jason Stevens
2019-06-26 0:53 ` Jason Stevens
2019-06-25 7:49 ` Jason Stevens
2019-06-25 7:59 ` Andreas Grapentin
2019-06-23 22:08 Noel Chiappa
2019-06-23 23:54 ` Theodore Ts'o
2019-06-24 17:04 ` Jason Stevens
2019-07-01 13:20 Jason Stevens
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=20190626025646.GR925@mcvoy.com \
--to=lm@mcvoy.com \
--cc=rich.salz@gmail.com \
--cc=tuhs@minnie.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).