The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marshall Conover <marzhall.o@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Tom Teixeira <tjteixeira@earthlink.net>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SNOBOL and RATSNO
Date: Tue, 9 Aug 2022 15:21:49 -0400	[thread overview]
Message-ID: <CAK0pxsENMkivOg7KL6dpH=eMyAB7KOW2yU9ACPq6Vbt-4tVTQQ@mail.gmail.com> (raw)
In-Reply-To: <20220809190028.GD21168@mcvoy.com>

> I've always believed that pic was so well designed
because it took a day to get the print out (back then), so you had to
have a language where you could see what it was doing.

> I'll confess: I was never very good at bench checking batch programs, but only had at most a handful of assignments in college: generally cycles were cheap on time-sharing systems and I quickly adapted to interactive debugging.

Along these lines, if I'm understanding correctly, my hunch would be
that part of the precision being discussed was born out of necessity.
When you can't debug interactively, you're forced to be precise with
your changes, influencing how you think. On the flip side, when
interactive development is an option, there's an easy route to take -
and so that's what ends up informing those developmer's thought
patterns.

I think it's possible that if you were to force a new generation to
only be able to iterate once a day, you may end up with a new
generation with that precision. Perhaps material for a fun experiment
for the teachers on the list.

Cheers,

Marshall

On Tue, Aug 9, 2022 at 3:01 PM Larry McVoy <lm@mcvoy.com> wrote:
>
> On Tue, Aug 09, 2022 at 02:54:08PM -0400, Tom Teixeira wrote:
> > On 8/9/22 2:49 PM, Larry McVoy wrote:
> > >On Tue, Aug 09, 2022 at 01:42:32PM -0400, Noel Chiappa wrote:
> > >>     > 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.
> > >I used to complain about this at Sun and was dryly told "We get it,
> > >Larry, you are yeast.  You need flour to make bread."
> > >
> > >And as time went on, I found that the smart people tended to find each
> > >other.  So it was fine.
> > >
> > >It is more fun when it is a highly curated group of smart people.  Made
> > >me work hard to keep up.
> >
> > Put another way, "If you're always the smartest person in the room, you're
> > spending your time in the wrong rooms."
>
> I was usually the dumbest one in the room, I found the right rooms :-)
>
> I personally like being "dumb", the other people just make you want to
> work harder to reach their level.  Back when I used to play pool pretty
> seriously, I always tried to play people better than me.  You get lazy
> if you are the best.
>
> --
> ---
> Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2022-08-09 19:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 17:42 Noel Chiappa
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 [this message]
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='CAK0pxsENMkivOg7KL6dpH=eMyAB7KOW2yU9ACPq6Vbt-4tVTQQ@mail.gmail.com' \
    --to=marzhall.o@gmail.com \
    --cc=lm@mcvoy.com \
    --cc=tjteixeira@earthlink.net \
    --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).