BUILDING SPEED #9

QUICK TIP

To produce a first-pass realtime transcript, you have to include necessary punctuation and required capitalization AS YOU WRITE. Do you always remember to include your "cap next" stroke when needed? I don’t <sigh>! It would never occur to me to not hit the "cap" key when typing, but I still forget sometimes that, unlike the shorthand I learned a million years ago where we didn’t even think about capitalization when writing, if I want a first-pass realtime record, or even avoid a lot of editing on a draft, I have to remember my "caps next" stroke.

Now (hurrah!) some CAT programs have a "retroactive capitalization" function—you can execute strokes to prompt the computer to RETROACTIVELY capitalize one, two, or three words. It’s simpler to depress one stroke and capitalize the previous three words than to stroke a "caps next" stroke before EACH of those three words. Plus, if you don’t realize until AFTER you’re in the middle of stroking, for example "great western land" that it’s a proper name, you can capitalize it retroactively and it will appear correctly as "Great Western Land" without having to asterisk out and restroke.

GREAT FEATURE! Keep it in mind when shopping for software.

Another MAJOR area of hesitation when writing machine shorthand is the hesitation involved in trying to decide WHERE to break words into shorthand strokes. The decision can be as simple as whether to break "filter" into strokes as FIL ter or FILT er. Without guidelines, even a common word such as "carpenter" could be broken into strokes as CAR pen ter, CAR pent er, CARP en ter, CARP ent er. With some "big" words, there could be as many as three or four decisions to make, with as many as 10 or 15 different ways the word could logically be broken into shorthand strokes based on any particular theory. That’s a lot of decision making, hesitation, LOST SPEED—and a very big incentive to scramble looking for a memorized brief form.

Many of you will already have been instructed by your teacher to "carry each stroke as far as possible through the sound of the word." That’s good advice. I expand on that a little and say: (1) If, based on the sound of the word, you have a logical choice as to whether to end a stroke before or after a consonant, end it AFTER the consonant (e.g., major = MAJ or, not MA jor); (2) If, based on the sound of the word, you have a logical choice as to whether to end a stroke between two consonants or after the consonant combination, end it AFTER the consonant combination (e.g., carton = CART on, not CAR ton). But basically, it does come down to the same thing: Carry each stroke as far through the sound of the word as possible.

WHY? First and foremost, it gives you a consistent guideline to follow so you’re not hesitating on every word of more than one stroke while you try to decide what’s the best way to stroke it. And there’s a lot to be said for "consistency" and what it contributes to speed. If you decide, for example, that you ALWAYS break strokes AFTER a specific consonant combination—say, the -rb—you’ll develop an automatic response to hearing -rb and your fingers will immediately automatically move to that stroking position. If you DON’T make and follow such a decision, when you hear -rb, your fingers can’t even start to move until after you take TIME to make a CONSCIOUS decision on how to write that consonant combination for this particular word or in this particular instance. That’s lost speed!

Also, on many words, when you carry strokes through a consonant combination, it simplifies the sound, reduces the number of strokes, and reduces spelling dependency. Let’s still use

-rb as our example, and let’s assume you’ve decided you’ll consistently carry strokes through an -rb combination. On a simple word like "carbon," the difference between breaking it as CAR bon or CARB on may not seem like a big deal. (There IS a difference in stroking "efficiency," and we’ll talk about that in a minute.) But now look at "carbonate." Because you’ve trained yourself to "hear" and stroke -RB instead of -R/PW-, you’ll react to that word as KARB uh nayt, and immediately recognize that you can omit that "uh" sound syllable (remember the elision principle?) and just stroke KARB/TPHAEUT If you DON’T carry the stroke through the -rb, you have to decide whether to stroke KAR bon ate or KAR bo nate, either of which requires an additional stroke. Lost speed! Plus, if you write a spelling-dependent theory, you have to know how that "uh" vowel sound is spelled and conform your stroke to the vowel spelling. Sure, you know how to spell "carbonate." But English is funny. That "uh" vowel sound can be spelled with any vowel and several combinations of vowels. How many words are you going to run into where you don’t know how the "uh" sound is SPELLED, where you have to think about it or guess at it? Lost speed!

And what happens when you get to even more complicated words like "carboniferous"? If you follow the guidelines, "carboniferous" is a breeze to hear and stroke: KARB/TPHEUFRS. Without any guidelines, there are a dozen different ways it could be stroked, with a number of decisions to be made and some spelling to think about. Lost speed!

Another reason for carrying the stroke as far through the sound as possible is that it may prevent conflicts which exist in a spelling-dependent theory—and conflicts are the nightmare of the realtime writer. Let’s take a couple of our earlier examples and use them again here. We have to assume that every computer-compatible theory has eliminated the conflicts between vowel-consonant word beginnings and endings (er-/-er, or-/-or, em-/-em, in-/-in,

al-/-al, etc., etc.) So if you follow the guidelines and break "filter" as FILT er, you won’t have a conflict. If you write a spelling-dependent theory and you stroke "filter" as FIL ter, those are the identical strokes you’d use to stroke the word "fill" followed by the word beginning "ter-." When CAT software translates steno, it keeps checking the next stroke, and the next stroke and the next stroke to see if including that next stroke would create a word. So if you stroke "fill" followed by any word starting with ter-, it will mistranslate as "filter": e.g., "Fill terrible gaps" will miss translate as "Filterable gaps." KART/ONZ won’t create a conflict, but KAR/TONS can create a conflict with "car tons." Other examples of possible conflicts when strokes are not carried as far as possible through the sound (always depending on the particular theory) are : candid/can did, carbide/car bide, bargain/bar gain, damper/dam per, damsel/dam sell, feces/fee seize, futile/few tile, gastric/gas trick, global/glow ball, guidance/guy dance, gypsum/gyp sum, halo/hay low, hamper/ham per, helper/hell per, hermit/her mitt, hyper/high per, jargon/jar gone, judo/Jew dough, kilo/key low, Kuwait/cue wait, latents/lay tents, license/lie sense, lilac/lie lack, masons/may sons, etc., etc.

Also, carrying strokes as far as possible through the sound frequently results in increasing stroking "efficiency." For example, carrying a sound through the consonant and stroking the consonant with what would otherwise by idle fingers on your right hand may require less dexterity and actually be faster than carrying the consonant sound over to the next stroke and having to reposition the fingers of your left hand to stroke it. Example: It may be faster for you to stroke "caper" as KAEUP/-R, than to stroke KA/P-R, placing the responsibility for stroking both the K- and the P- on the left hand while your right-hand fingers sit idle. Carrying strokes through a consonant sound and stroking the consonant with the right hand frequently involves fewer fingers, traveling a shorter distance, than carrying the consonant sound over to the next stroke and stroking it with the left-hand fingers. Try it. The difference may be very slight but still noticeable to you. Logically, the fewer fingers you must move, the shorter distance your fingers have to travel, the faster the strokes can be executed and the less the likelihood of stroking error.

And please remember, I said when you have a logical choice, based upon the pronunciation of the word. You don’t have to force words into some distorted pronunciation just so you can carry the stroke further through the sound. Nor do you have to make an absolute rule that you always carry a stroke through EVERY consonant combination. We each have particular fingering strengths and weaknesses. For example, it may be faster for YOU to break strokes BETWEEN a -kt consonant sound. The important thing is that you make decisions on how it’s best for YOU to handle specific sounds that can impact many words rather than having to make individual decisions on every word which contains those sounds. And in those areas where you can train yourself to HEAR through the sounds and carry each stroke as far through the sounds as possible, it can simplify the hearing, reduce the number of strokes required, reduce the decision-making, reduce the spelling dependency, and avoid a few conflicts. All of which can contribute to writing speed.