The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Stories
Date: Wed, 05 Dec 2018 22:22:58 -0500	[thread overview]
Message-ID: <201812060322.wB63MwGn025254@tahoe.cs.Dartmouth.EDU> (raw)

> So how was it that so many smart - and somewhat like minded it seems
> people end up there? [At Bell Labs]

1. Bell Labs had a great reputation, though it was not at first known
   for computing.

2. Research recruiters were researchers themselves, not HR people.

3. Recruiting was for quality hires, not for particular jobs;
   complementary talent was valued.

4. Whom a candidate met on site was determined after s/he gave a seminar;
   this promoted good matchups.

5. Researchers decided for themselves what to work on--either self-
   generated or an interesting problem from elsewhere in the company.

6. If you needed to know something in most any field, you could usually
   find a willing expert to get you on track to an answer.

7. Annual merit review was collegial. No one lost out because of unlucky
   draw of a supervisor.

8. Collegiality in fact beat that of any faculty I know. Office doors
   were always open; new arrivals needed only to do good work, not to
   chase tenure. 

This culture grew from the grand original idea of the Labs: R&D for
the whole of AT&T funded by the whole of AT&T, with a long time horizon.
I joined thinking the Labs was good seasoning for academia. The culture
held me for 39 years.

The premise was viable in the days of regulated monopoly. It has been
greatly watered down since.


Doug

             reply	other threads:[~2018-12-06  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  3:22 Doug McIlroy [this message]
2018-12-06 19:26 ` arnold
  -- strict thread matches above, loose matches on Subject: below --
2018-11-28 17:17 [TUHS] stories Larry McVoy
2018-11-29  7:20 ` Kevin Bowling
2018-12-06  0:37 ` Steve Johnson

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=201812060322.wB63MwGn025254@tahoe.cs.Dartmouth.EDU \
    --to=doug@cs.dartmouth.edu \
    --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).