Home     Contact Us    
Main Board Job Seeker's Board Job Wanted Board Resume Bank Company Board Word Help M*Modal Nuance New MTs Classifieds Offshore Concerns VR/Speech Recognition Tech Help Coding/Medical Billing
Gab Board Politics Comedy Stop Games Faith Board Prayer Requests Health Issues

ADVERTISEMENT



Main Board

Because typing speed doesn't have as much to do with line count - sm

Posted: May 18th, 2016 - 4:04 am In Reply to: Anyone else make shortcut upon shortcut but their lines stay the same? - How is this possible?

as some people think.

First, of course, if you are editing VR instead of doing straight typing, the shortcuts that will do you good are for editing, not typing.

If you are doing straight typing, what's your line count per hour, and how much does that have to do with your typing speed?

If you type 80 wpm and all you were doing was typing as fast as you could, you would be able to produce 500 lines per hour. The reason everyone doesn't do 500 lines per hour without even breaking a sweat is the starting, stopping, replaying, checking, researching, etc. Creating typing shortcuts only increases your typing speed. It doesn't do anything for what is sucking up the rest of your time.

Say you, with your theoretical 80 wpm typing speed, are producing 250 lines per hour. That means your effective transcription speed is not 80 words/8 lines per minute, but only about 40 words/4 lines per minute. If you create enough shortcuts to reduce your total keystrokes by 25%, which is a LOT of shortcuts, that goes up to only about 50 words/5 lines per minute, or another 60 lines per hour--not that big a difference.

So, what is your typing speed in words/lines, what is your effective transcription speed in words/lines, and what total percent of keystrokes are those "shortcuts upon shortcuts" saving? Are you actually seeing less of a change in effective transcription speed than that keystroke saving should give you?

ADVERTISEMENT


Post A Reply Reply By Email Options


Complete Discussion Below: ( marks the location of current message within thread)