Developers key in lots of code, write bogs, write software designs and stuff. Do we need formal typing training? I have seen many developers struggling with keyboard thus slowing down development momentum. At least we can play around with a software typing emulator to begin with.
|
|
Need? No. Would benefit from? Yes absolutely. Developers need to be able to type fast or perhaps "efficiently" (that implies an adequate level of accuracy) - although much of what we type doesn't necessarily lend itself overly well to classic typing skills. I can sort of almost touch type - I don't need to look at the keyboard much... combination of various stalled attempts to learn (initially on a real typewriter!) and 30 years of practice teaching me where all the keys are... |
|||||||
|
|
Do more typing. You get better with practice. By all means use a typing tutor if you think it will help, but practice does help. |
|||||||||||
|
|
Considering that on average a developer produces only ~10 LOC per day, I'd say that your typing speed is not that important. Hence, formal training is not needed. |
|||||||||||||
|
|
If it's holding back your productivity, than it would be useful to get some training. I type a tad faster than I can think (30-40wpm), so I don't think I really need to learn to type any faster. I made myself learn to type properly. Not touch typing, but just using all my fingers. That alone will help speed considerably. If you only use thumb and 2-3 fingers, I'd highly reccommend that you try to learn to use the others as well. It will slow you down at first, but speed you up in the long run. It's like multithreading - more processes mean faster processing! |
|||
|
|
|
I would like to add: You don't need formal training, if you mean having another person tutor you. You can use free or proprietary training software. I imagine you spend some amount of time typing e-mails, reports, and documentation. The greatest devourer of your typing time besides simply typing too slow is making errors. (For every error, you must stop, reach over and backspace or CTRL+Shift+LeftArrow, and re-type the same thing. The cumulative effect is great.) |
|||
|
|
|
anecdote: About 8 years ago, when I was in school, my programmer friends and I would have programming competitions. We were all eager programmers, so when we got an assignment, we'd hit the keys right away working on that assignment right away. Mysely and 2 others in the group were 100+ wpm typers. 3 people in this group consistently won these competitions of ours. Two fast typers and one slow typer (I mean, ridiculously slow, he had a physical disability such that he typed 15wpm tops). That slow typer was an awesome programmer. Moral of the story: If you know what you're doing, typing fast is will let you stomp your programming competition. But first you have to know what you're doing. |
|||
|
|
|
Just make sure that you don't end up being able to type faster than you can think :-D Thinking-speed is probably the limiting factor for most of us developers! |
|||
|
|
|
I don't think you need formal training, just try and program little personal side projects and in time you will notice an improvement in your typing skills. Also in time you will notice that most of your programming does not consist in typing the code but thinking of the correct solution. |
|||
|
|
|
IMO you should be really good in typing, i.e. you should not have to think about the keyboard or look for keys. Formal training... well, I had to do that, and it sucked, because it was really unforgiving regarding typos; having something like 5 typos on a whole page of paper was enough to fail a test. The important thing is that I knew I had made those typos, but could not correct them (there was no correction key on the typewriter); it's like having a keyboard without a backspace key. I can only hope that this part has changed since. |
|||||
|
|
Like anything in programming, if you can't figure it out on your own, get some help. You may spend less time on SO sites ;) |
|||
|
|
