|
For me not, 
I improved my speed by simply programming, and some years.
|
|
|
|
|
...not because you can bang out the code faster, but because banging out the code is less of a distraction. I've too often seen programmers carefully consider a technique, or look up an API, and then start writing out the code... only to pause a minute later because they'd forgotten something while pecking out the syntax.
Regardless of whether you're using two fingers or ten, if the keyboard is your primary method of communication you shouldn't have to think about it (much less look at it) any more than you should need to think about pronunciation while speaking in your native language.
|
|
|
|
|
I like this response. Eliminating distractions is a vital skill for programming, you can't afford to waste brain-cycles looking for keys. That being said, I don't know if it would qualify as touch typing - I've never seen the textbook way to press Ctrl-Space for example.
|
|
|
|
|
Hei that's true, every time I've seen combinations of keys, they never teach you the best way to push them.
|
|
|
|
|
fast, but sometimes intellisense does not help me to much  luisnike19
|
|
|
|
|
I've found with VS2008, sometimes you have to press other keys (esc) so as to cancel Intellisense from doing something - maybe you want to write a small word or variable and a longer keyword or variable pops up - meaning that unless you press ESC before you press SPACE (to end the short word), the Intellisense expands your word to one you didn't want.
I love Intellisense but hate recent implementations too.God is REAL unless declared int
|
|
|
|
|
| Yes, I also have the same problem but with SQL 2008 luisnike19
|
|
|
|
|
Some years ago I had to write a software training system that taught people how to touch type. Yes it was necessary as the end result was not normal text but special codes made up of alpha numeric combinations; regular touch typing was just a precursor to that.
The consequence is that I know how to touch type and understand all the theory and practice and yet I never seem to have had the time to use it enough to improve my speed to an acceptable standard. I have made an effort many times but usually have to get the document done and do not have the time to mess about.
I type with about four to five fingers and am fairly fast, the downside is I have to look at the keyboard and that is something touch typing would overcome. It’s a real nuisance when you have typed a chunk of text and then find caps lock is on or some such that has screwed up the result.
Not much benefit when coding, which is how I spend most of my typing time, as typing fast achieves little but for documentation etc, etc,and we all have to do some of that, it can be a real plus.
|
|
|
|
|
I make lots of typos.... I wonder how much work I'd get through if i didn't have to backspace or type things twice 
|
|
|
|
|
backspace accounts for probably close to a third of my total keystrokes; I wonder the same thing. I test at about 65wpm including all the backspacing though, so with all the fast and furious key-pounding I'm able to seem a lot faster than I actually am
|
|
|
|
|
|
I can touch type fast, but moving from one keyboard to another, desktop to laptop, or client computer, I get Fat Finger Syndrome.
Also I think the neurons must be faster for one hand than the other causing keyslexia.
A friend of mine came from the teletype world... his hammertyping would wear out keyboards in short order.modified on Monday, March 15, 2010 10:46 PM
|
|
|
|
|
See! I told you I cluod tyep reall fast! I sometimes type so fast that I spend 50% of my time on the backspace key. Now that is productivity at it's finest! I hate strange keyboards, like at a client office, where ones hands start to shake and bounce on those ultra-sensitive (aka: not beaten into submission yet) easy to press keys. Makes me smoke! Trust the force, that's my motto. If you are not using enough force to make your desk shake, then you are just babying your keyboard and it will push you around and insert errors into your code. 
|
|
|
|
|
In my career i saw a lot a programmer typing at the speed of light ... and 80% of the time finger on backspace and all kinds of stupid compiling errors. Typing fast is not the only solution.. plenty of keyboard Shorcuts with Visual Studio in order to increase productivity.
|
|
|
|
|
I agree with the point of using shortcuts but undoubtly having good typing skills can help you 
|
|
|
|
|
| Here I thought touch-typing meant on like an on-screen display for a phone with no physical keys. Jeremy Falcon
|
|
|
|
|
I thought the same thing 
|
|
|
|
|
I suppose that i can now type with out hunting for the keys. As my keyboard has now
Two ‘P’ and a rapidly disappearing E and slightly sickly looking A,S,D,O
|
|
|
|
|
but the main input is mouse 
i move it fast, clicking uber fast d{^__^}b - it's time to fly
|
|
|
|
|
On-Screen Keyboard for the win!
|
|
|
|
|
| Well maybe a little less fast since I use visual assist all the time to complete identifier names... John
|
|
|
|
|
Agree... I am definately slower at touch typing since using VA for a few years. 
|
|
|
|
|
After twenty-five years of it, I have become very good at typing one-handed -- I neither hunt nor peck.
Programming isn't like "normal" typing; it goes in spurts, doesn't utilize regular words and capitalization, and contains a lot more digits and special characters.
|
|
|
|
|
PIEBALDconsult wrote: I have become very good at typing one-handed
What're you doing with the other hand. 
|
|
|
|
|
I am not really slow but I am not fast either. I do around 30 to 40 wpm. I guess I am thinking more in line with general typing than with programming, but the only class in high school that was worth anything was personal typing (no computer classes back then).
My other problem with typing speed is my memory is bad at best. As long as I am doing code that is familiar I am okay but I tend not to remember common syntax.
djj
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
