Kevin:
 
Sorry if I offended in any way; that was not my intention.  I learned to type 
in high
school.  Typing got me a cushy job in the military.  It got me extra money 
through
college.  When one learns to type two characteristics stand out; hands rest on 
the
keyboard and eyes are generally looking elsewhere.
 
Given this, it's understandable how two finger typing creates a certain "point 
of
view."  That was my point, which I so ineloquently made.   Two finger typing 
doesn't
create the same operating environment learned typing does (noted above).  The
environment of both realities are much different; hence I have no frame of 
reference
of watching each keystroke I type (it is often when I press the [Enter] key and 
I
hear some sound that alerts me to the wrong case).  Hence, my comments were 
made from
the reality of a typist.
 
As for your challenge, I'd be happy to take you up on it where we pit one who 
types
against one who doesn't to see who can type a printed document the fastest.  
There's
a lot of literature regarding the vast improvement in efficiency of learned 
typists
over those who can't type.  That's a pretty unfair challenge.   However, if your
challenge is that you're a more effective programmer than me I'll have to 
concede (as
I would to most on this list); I had to work too hard to get through college 
and have
a very difficult time working in an OOP development environment.  :-)
 
So, I'll agree to concede that for two finger typists, the status of the [Caps 
Lock]
is mostly irrelevant?  While you can concede that for those who can type, and 
don't
look at what they're typing too often, [Caps Lock] on can present a problem.
 
Agreed?
 
Bill


  _____  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Kevin King
Sent: Monday, March 10, 2008 6:12 AM
To: [email protected]
Subject: Re: [U2] blank lines in code / mixed case



Bill, I followed you until this:

* Upper case is an anachronism and should be treated as such rather than 
defended.
It
is unwieldy for far too many and, in fact, interferes with efficient typing at 
every
turn.  Forcing people to use [Caps Lock] in U2 while all other used applications
require [Caps Lock] to be off is a egalitarian ruse for autocracy.  :-)
*
While I understand this is intended to be slightly tongue-in-cheek, saying
that it unequivocally "interferes with efficient typing at every turn" is
quite possibly much more generalized of a statement than the discussion
warrants.  While I agree with your assessment about the mix of applications
that we are using at any given moment which are using the caps lock in the
off position, I find this to be a non-issue and rarely miss more than a
couple of characters when switching between apps.  For me personally, a
couple of caps mistakes a week beats the thousands of times pressing the
Shift key where I - notably a two-finger typist - have to get both hands
involved.

But rather than rely upon conjecture, why not actually test this theory?
Let's setup a meeting at Spectrum where we each create a simple sample
program using our case of choice, and we'll appoint an "official" timer to
see which method produces the fastest results.  Game?

-K
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to