The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: SNOBOL and RATSNO
Date: Tue,  9 Aug 2022 13:42:32 -0400 (EDT)	[thread overview]
Message-ID: <20220809174232.A882C18C08A@mercury.lcs.mit.edu> (raw)

    > From: Rob Pike

    > I still marvel at the productivity and precision of his generatio

We noticed the same thing happening in the IETF, as the number of people
working on networking went up. The explanation is really quite simple, once
you think about it a bit.

If you have a very small group, it is quite possible to have a very high
level. (Not if it's selected randomly, of course; there has to be some
sorting function.) However, as the group gets much larger, it is
_necessarily_ much more 'average' in the skill/etc level of its members.

This rule applies to any group - which includes the members of TUHS,
of course.

	Noel


             reply	other threads:[~2022-08-09 17:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 17:42 Noel Chiappa [this message]
2022-08-09 18:49 ` Larry McVoy
2022-08-09 18:54   ` Tom Teixeira
2022-08-09 19:00     ` Larry McVoy
2022-08-09 19:21       ` Marshall Conover
2022-08-09 20:19         ` Warner Losh
2022-08-09 20:43           ` [TUHS] mainframe $ budgets [was " Charles H Sauer (he/him)
2022-08-09 20:58             ` [TUHS] " Marc Donner
2022-08-09 22:49               ` Charles H Sauer (he/him)
2022-08-10 21:13 ` [TUHS] " Bill Cheswick
2022-08-10 21:30   ` John Cowan
2022-08-11 16:08     ` Marc Donner
  -- strict thread matches above, loose matches on Subject: below --
2022-08-09 22:18 Douglas McIlroy
2022-08-09 22:25 ` Larry McVoy
2022-08-10 15:05 ` arnold
2022-08-10 17:14   ` Larry McVoy
2022-08-10 17:37     ` arnold
2022-08-10 18:24       ` joe mcguckin
2022-07-23  2:57 [TUHS] Line Numbers Before SysIII nl? BSD num? segaloco via TUHS
2022-07-23  5:56 ` [TUHS] " markus schnalke
2022-07-23  7:55   ` segaloco via TUHS
2022-07-23 11:01     ` Dan Cross
2022-07-23 11:20       ` John Cowan
2022-07-23 12:00         ` Dan Cross
2022-07-24 19:02           ` Tomasz Rola
2022-07-28  0:30             ` Tomasz Rola
2022-07-28  1:03               ` Phil Budne
2022-07-28  4:13                 ` [TUHS] SNOBOL and RATSNO William H. Mitchell
2022-07-29  4:28                   ` [TUHS] " Dave Horsfall
2022-07-29  5:07                   ` Tomasz Rola
2022-08-09  5:12                     ` Jonathan Gevaryahu
2022-08-09  6:11                       ` Rob Pike
2022-08-09 13:34                         ` Clem Cole
2022-08-09 15:15                           ` Andrew Hume
2022-08-09 18:26                             ` Clem Cole
2022-08-09 18:52                             ` Tom Teixeira
2022-08-09 21:25                             ` Rob Pike
2022-08-09 15:39                           ` Richard Salz
2022-08-09 13:56                         ` Larry McVoy
2022-08-09 16:45                         ` William H. Mitchell

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=20220809174232.A882C18C08A@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.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).