The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Fri, 03 Feb 2017 19:46:47 -0800	[thread overview]
Message-ID: <fa16db67d666b506fc08a62b50a84b95f06d932a@webmail.yaccman.com> (raw)
In-Reply-To: <201702021311.v12DBNoa004846@freefriends.org>

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

About a decade ago, I attended a workshop at an Intel location in
Mass.  There were about 50 outside people.  We were in a rather nice
room across from a break room which provided coffee and sodas.

Just as we were about to start, someone showed up and informed us all
that the break room was for the exclusive use of Intel Employees, and
outside visitors were not permitted to use it.  And then they left. 
The Intel hosts rolled their eyes and set up a system whereby we could
ask an Intel employee to get us whatever we wanted from the break
room.  The workshop was pretty good anyway...

----- Original Message -----
From: arnold@skeeve.com
To:<lm at mcvoy.com>, <clemc at ccc.com>
Cc:<tuhs at minnie.tuhs.org>, <jnc at mercury.lcs.mit.edu>
Sent:Thu, 02 Feb 2017 06:11:23 -0700
Subject:Re: [TUHS] Names of famous, historical UNIX machines?

 Clem Cole <clemc at ccc.com> wrote:

 > On Wed, Feb 1, 2017 at 5:11 PM, Larry McVoy <lm at mcvoy.com> wrote:
 >
 > > I visited Portland and Santa Clara and I have never
 > > seen a more grey cubicle farm in my life.
 >
 > I don't remember which comic it was, but about 8-10 years ago one
the late
 > night comedy guys brought a film crew to SC and made that same
exact
 > observation.

 It was Conan O'Brien. You can find it on YouTube.

 > While Intel does do many things well, this one is part of company
culture
 > and I'm not in a position to change it. I wish I could.

 It's a huge blind spot for Intel. They tout it as "everyone is equal"
 but they miss that noone who needs peace and quiet to work can work
 productively.

 > I think the place
 > would be a small bit happier if it did not take itself quite so
seriously,
 > but that's just my personal opinion.

 Yes, as a fellow Intel employee, I'd have to agree.

 Sigh.

 Arnold

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170203/10fa7c35/attachment.html>


  reply	other threads:[~2017-02-04  3:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:43 Michael Kjörling
2017-02-01 20:46 ` Clem Cole
2017-02-01 20:50 ` Clem Cole
2017-02-01 21:11   ` Lars Brinkhoff
2017-02-01 21:20   ` Noel Chiappa
2017-02-01 21:42     ` Michael Kjörling
2017-02-01 21:43       ` Cory Smelosky
2017-02-01 22:16         ` Cory Smelosky
2017-02-01 21:50       ` William Pechter
2017-02-01 22:06     ` Clem Cole
2017-02-01 22:11       ` Larry McVoy
2017-02-01 22:21         ` Clem Cole
2017-02-01 22:28         ` Clem Cole
2017-02-01 22:44           ` William Pechter
2017-02-02  1:14             ` Rico Pajarola
2017-02-02  1:34               ` Clem Cole
2017-02-02  1:18             ` Clem Cole
2017-02-02  1:29               ` Clem Cole
2017-02-02 13:11           ` arnold
2017-02-04  3:46             ` Steve Johnson [this message]
2017-02-04  3:56               ` Larry McVoy
2017-02-04 22:48                 ` Nemo
2017-02-01 22:26     ` Arthur Krewat
2017-02-02  7:38       ` Lars Brinkhoff
2017-02-01 21:33 ` Larry McVoy
2017-02-01 21:57   ` Clem Cole
2017-02-01 22:08     ` Larry McVoy
2017-02-01 22:20       ` Steve Nickolas
2017-02-03  1:51   ` Dave Horsfall
2017-02-01 22:54 ` Jacob Goense
2017-02-03 12:59   ` Tim Bradshaw
2017-02-03 14:04   ` Dave Horsfall
2017-02-03 14:11     ` Jacob Goense
2017-02-03 15:12       ` Arthur Krewat
2017-02-06  5:41       ` Dave Horsfall
2017-02-03  5:50 ` Lars Brinkhoff
2017-02-01 22:16 Noel Chiappa
2017-02-01 22:27 Berny Goodheart
2017-02-02  9:59 Rudi Blom

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=fa16db67d666b506fc08a62b50a84b95f06d932a@webmail.yaccman.com \
    --to=scj@yaccman.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).