The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Larry Stewart <stewart@serissa.com>
Cc: steve jenkin <sjenkin@canb.auug.org.au>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Wed, 2 Nov 2022 06:16:34 -0700	[thread overview]
Message-ID: <20221102131634.GF26791@mcvoy.com> (raw)
In-Reply-To: <7A8AFF11-5383-4FD3-8FA4-D262B30DC6A1@serissa.com>

Self taught touch typer here.  I frequently compare typing to running
my excavator.  If I don't think about what I'm doing, everything works,
I can type in the dark (doing that right now) but as soon as I start
thinking about where the keys are (or what the joysticks on the excavator
do) it all goes to shit.

And getting back to writing, I personally feel like if you write the 
man page first, it settles my messy brain into a good space, the code
comes easier after writing docs.  I view writing docs as sort of the
first pass of thinking about how to write the code.  Doesn't always
work but it is pleasant when it does.

On Wed, Nov 02, 2022 at 09:07:31AM -0400, Larry Stewart wrote:
> In 1969 at the end of 9 th grade I got a foot injury that kept me on crutches for the summer so I took summer school typing. very worthwhile. I think 90% of the class were young women. My parents encouraged it mostly because it would make  writing term papers much easier, which it did, but of course it had many computing benefits as well.
> the ancient typewriters had really heavy keys with long strokes. Much like teletypes.
> 
> > On Nov 2, 2022, at 8:27 AM, John P. Linderman <jpl.jpl@gmail.com> wrote:
> > 
> > ???
> > When I was in high school (in the early sixties) I tried to sign up for typing, which was taught on manual typewriters. I was told that the class was for girls only, and I was turned away. I never did develop good typing skills. I'm pretty much a two-fingered typist. Ironically, I have probably done more typing than 90% of the female classmates who were allowed to take the class.
> > 
> > Precision figured mightily in those days, which may also have pre-dated white-out. Eliminating an error was a big deal. Now it's dead easy, and auto-correct has already fixed several errors in this message. 
> > 
> >> On Wed, Nov 2, 2022 at 8:14 AM Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
> >> steve jenkin wrote in
> >>  <E212D205-B786-4441-A95B-B5F5546B5C6C@canb.auug.org.au>:
> >>  ...
> >>  |I???ve never heard anyone mention keyboard skills with the people of \
> >>  |the CSRC - doesn???t anyone know?
> >> 
> >> What i personally find more fascinating (given that -- in the
> >> right condition -- i type pretty fast even in total darkness but
> >> darkest possible monitor brightness) is the multitaskability some
> >> show, in respect to combination of mouse and keyboard (or even
> >> dual-mouse if i remember a message of Rob Pike right).  I once
> >> watched a video on the google tube of Russ Cox dancing acme doing
> >> go testing, could be it is [1].  When he starts to actually work
> >> a bit (late on iirc), that is thrilling, i could never select /
> >> paste (kill snarf yank what do i know) that fast.
> >> 
> >>   [1] https://www.youtube.com/watch?v=dP1xVpMPn8M
> >> 
> >> --steffen
> >> |
> >> |Der Kragenbaer,                The moon bear,
> >> |der holt sich munter           he cheerfully and one by one
> >> |einen nach dem anderen runter  wa.ks himself off
> >> |(By Robert Gernhardt)

-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2022-11-02 13:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy [this message]
2022-11-02 13:27     ` Steffen Nurpmeso
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas McIlroy

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=20221102131634.GF26791@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=sjenkin@canb.auug.org.au \
    --cc=stewart@serissa.com \
    --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).