below 15wpm
15-35wpm
35-55wpm
above 55wpm!
>> So, according to the test, 53 WPM with 6 errors. Many more errors that I corrected while typing - my main problem is inaccuracy.
And is this by touch or hunting/pecking?
>> Never done a test, and my writing limit is usually limited more by my thoughts than by my fingers
You generally come across as rather articulate, so maybe that's a good thing.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
Touch, but I lose really a lot of time because I notice my errors by touch, too, and can't go on when I make one.Originally Posted by Sebastiani
>> Never done a test, and my writing limit is usually limited more by my thoughts than by my fingers
You generally come across as rather articulate, so maybe that's a good thing.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
62 wpm, with 100% accuracy; I made two mistakes but corrected them. However I think that type test can never be completely accurate; apart from the fact that you type a lot faster when you type from your head, it also depends on what the type test wants you to type; it can give you sentences similar to "George ate an apple and threw up." or sentences like "Cryptographically secure linear feedback shift register based stream ciphers". Also, I don't know about you guys, but I'm extremely nervous when I do a type test, and specifically with this one could feel that I wasn't typing 100%.
Cheers,
Gabe
On the other hand, we have the advantage of not being too used to a specific form. I've been typing both "color" and "colour" forever.This makes me commend our forum members who are not native English speakers getting good results on these tests.
All the buzzt!
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
I suppose that's true, but don't you find yourself sometimes typing "Farbe?"
I agree when you have no habits, it's probably easier... and I would also say that it would be easier for most non-native English speakers to type in English than most English speakers could in a foreign language simply because no matter where you are in the world you're seeing and hearing English a lot at a very young age. I still believe typing in a second language puts you at a decent disadvantage than when typing in your primary language. Since I've made my post I found a test that allowed me to type in another language that I know. I took the test a few times with a few different passages and ultimately I found myself with a 10WPM decrease.
Sent from my iPadŽ
>> I still believe typing in a second language puts you at a decent disadvantage than when typing in your primary language.
Yup. Except when it's funny, like when the menu at a Chinese restaurant says "Killing Duck on Spit" or "Puchase with crediT MORE expensive".
>> I'd say I'm more of a seven finger typist.
Wow. Like Liberace!
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
If I am generating original text, I can hit 120 wpm, but I usualyl hve to go back and fix the typos. I never have been good at transcription.
Not in English. Perhaps if I were typing in French. But when I use English, I'm actually completely switching to the language, including thinking in it.I suppose that's true, but don't you find yourself sometimes typing "Farbe?"
All the buzzt!
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
From the page linked.Your speed was: 95wpm.
You made 3 mistakes, your mistakes are shown in bold text:
Let the reader be introduced to Lady Carbuy, upon whose character and doings much will depend of whatever interest these pages may have, as she sits at her writing-table in her own room in her own house in Welbeck Street. Lady Carbuy spent many hours at her desk, and wrote many letters wrote also very much beside letters. She spoke of herself in these days as a woman devoted to Literature, always spelling the word with a big L. Something of the nature of her devotion may be learned by the persual of three letters which on this morning she had written with a quickly running hand.
Touch typing of course
*edit*
Oh and, English is not my native language. My native language is Chinese, though, and typing in Chinese is certainly quite different from typing in English (more different than, say, between English and French or other European languages).
I think my main barrier is not being able to read ahead too much. Typing alone takes too much CPU time already. It should be a lot faster if I memorized the passage. In a sense I am doing reading-typing-reading-typing alternatively, one word at a time, as opposed to asynchronously
Last edited by cyberfish; 11-22-2008 at 04:22 PM.
It would be, but that's not the point of the test. The idea is to be able to transcribe what you're seeing regardless of whether you've seen it before or not. You can take that same test with the same passage a dozen times and on the last time you'd probably increase your typing speed by 15-20WPM. This is why a really good typist should pretty much be able to type any language, barring any non-English characters, regardless of whether they know the words or not, at very fast speeds. Like most others in this thread have said, already... they, I, and most average typists are much faster typing something original from their head than they are transcribing some text they've never read. It's commonly seen as a good thing, but from a purely typist prospective, the few I've spoken to (secretaries and such whom I've seen type close to 110-120WPM) would tell you that when transcribing you shouldn't even look at the word, but rather just the individual character.It should be a lot faster if I memorized the passage. In a sense I am doing reading-typing-reading-typing alternatively, one word at a time, as opposed to asynchronously
Sent from my iPadŽ
Wouldn't reading faster actually help you type faster? Because generally you don't look at individual characters when reading, but rather the whole word.
It does make you faster, as I said because it allows you to read ahead, but it also makes you susceptible to habit. While it will increase your speed in words your familiar with, if you are typing words that you are unfamiliar with it will decrease accuracy which ultimately decreases speed when your transcription needs to be perfect. This is how I've been told. Like I posted in my example before, if I see the word "thy," my brain automatically thinks "they" and types it. This is a problem and my eventual results showed that. Reading ahead sounds like a great thing, but for transcription it's not. It's the equivalent to a comprehension rating in reading speeds.
Sent from my iPadŽ
I've only been able to touch type for a about 3 years now, and I really can't do it that well on a keyboard that I haven't familiarized myself with. My slow development is probably due to the fact that I didn't learn "properly". You know, like from a program that tells you what finger goes where. I just kind of "figured it out".
I average on 35-55wpm (most correct)... but I'm faster at writing C.
It is strange though, how you can type any letter and/or word that you want just by thinking it, yet I couldn't tell you the location of every letter on the keyboard.
It's the difference between muscle memory and visual memory. Two completely different parts of the brain. Think about how many times you've written a particular word vs. the number of times you've studied a keyboard's key positions. When your brain thinks of the word you want to type it doesn't visualize the keyboard at all, it simply remembers what your hands are supposed to do when you type the word. Have you ever noticed that when you try to type a word you aren't quite familiar with that you kind stutter thinking about where to press your finger next? Maybe you even look down at the keyboard? Just the way the body and brain works.
Sent from my iPadŽ
That said I find this website helpful in learning key positions and working with practice text to learn to touch type. What holds me back is bad dexterity, honestly.
