|
Posted by Sanders Kaufman on 09/26/07 11:15
"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:f5ydnaUMj6ZVW2TbnZ2dnUVZ_ramnZ2d@comcast.com...
> Sanders Kaufman wrote:
> I'm a touch typist - and as I said above, I'm often not looking at the
> screen when I'm typing. And I can finish the function name by typing it
> in much faster than I can look at the screen, hit a couple of down arrows
> and a tab.
>
> Sure, I occasionally misspell a command. But I'm still faster typing it
> out than with some code completion.
>
> Don't get me wrong - it's great for the "poke and hope" typists. But when
> you're moving along at > 80 wpm, it's a tremendous slowdown.
I'm a touch-typist, as well - 100WPM 10 years ago.
If you add mastery of 21st century code-completion, to mastery of 19th
century keyboard layout - you can cut your keystrokes nearly in half.
All the kids are doing it these days.
>> Beyond that, I sometimes use variable names that are spelled the same,
>> but capitalized differently.
>> Code-completion pops up to show which variables are defined - with the
>> defined capitalization.
>> So it not only helps in avoiding misspellings, but miscapitalizations as
>> well.
>
> I don't do that. I have a system on how to capitalize variables, and use
> it consistently.
> But the secret here is to be consistent. However you do it, ALWAYS do it
> that way.
Hmmm - I've always thought the key to being productive was versatility.
Breadth vs. depth - it's a timeless question, ain't it?
[Back to original message]
|