Now that I actually have time to update, I seem to be more interested in making notes about things I want to include. I was starting to feel like it was pointless because I never had time to write about anything. Maybe I'm just noticing more things now that I'm able to see more mistakes.
I picked up a cool tip from Kosmo's Korner, and it wasn't even the feature of the vlog. During one of the videos, he mentioned hitting "H" twice to mark two words next to each other, and it's an awesome hyperkey. Before when I wanted to global something, I had to navigate to the last word in the phrase, and sometimes I had to use Ctrl + left arrow to get there, and it was a huge pain.
Plus, even if I was at the beginning and I pressed "G" to global, sometimes it would only pick up the first stroke, even though it had combined two strokes into one word, and I had to hit escape and navigate to the end of the word, G, and then up arrow to pick up the first stroke. But now I can just type H, and it picks up the entire word; and if I hit it again, it picks up the next word, for as many words as I need! It's so much easier.
I had a weird problem where I couldn't get re-present (as in present again) to come out because "represent" is also a word. I tried manually writing the hyphen, so of course that didn't work. So I had to define RE/H-F/PRENT as "re-present." I also realized as I was going through a transcript that someone said "and you, Tara," and I thought they said a name I had never heard before, "Utara." There are so many names I haven't heard, and there are a lot of international students in that class. I didn't bat an eye fingerspelling "Utara," but I was so embarrassed when I figured it out later!
I learned A*B as "Alabama," but I changed it a long time ago to "an," with A*EB for Alabama. For some reason, I always think of Alabama as BA*EM, but that's not defined as anything, so when I'm writing I just have to delete it and write A*EB. And it finally dawned on me - why don't I just define BA*EM as "Alabama"? There wasn't anything strategic about using A*EB, so if it didn't work, there's no reason not to change it.
One of the things Word spellcheck catches that Eclipse spellcheck doesn't (probably because I don't have it set to) is repeated words. Sometimes I'll stroke my brief for "of the" and then I'll also stroke "the," and I don't write it when people repeat words like that, so there's no reason not to just define OF-T/T as "of the." After doing that for a long time, I finally thought, why not take it a step further? Because then I wind up writing "are the the," and I have to define "R-T/T" as "are the," but I could take all that out of the equation by just adding the the=the to my autoreplacements table, or making a text global for I I = I, both of which I did (because for some reason the I I=I didn't work in the table).
I come up with a lot of briefs, and they seem like a great idea, but then I totally forget about them, and down the line I think I need to come up with a brief for something, and stroke my idea, only to find out that I already made it. Sometimes I would put a new brief on my "to practice" list, but I never made it a routine, so I'm working on doing that now. I think it will help things "stick" a lot better.
Speaking of briefs, I learned DAOIGS for "diagnosis" in school, and I stroke it pretty much every single time when I try to write "diagnose," which comes up a lot more often than "diganosis." I decided to leave DAOIGS as "diagnosis" since that's what I was taught, thinking maybe it's ingrained somewhere, but I finally made "diagnose" DAO*IGS, and it's so nice not worrying about what's going to happen when I write DAOIGS anymore.
I also put in KPAOUNGS for communication and THAO*IVG for Thanksgiving. I have 30 different outlines for Thanksgiving, and I'm still writing it in ways that don't come out right. I put THA*FG in as a brief for it last year (and wrote it exactly 0 times), and that obviously didn't stick, so I'm trying THAO*IVG. We'll see if it conflicts with THAO*EVG for "thieving."
I had to change N-G from "inning" to -ing in, because I was stacking it like crazy. I think it might have something to do with gradually turning that minLR up, because I only just started noticing it. I still have it set below the default, though. I'm also stacking THAS a lot, but I'm not changing it from "that is" because I've written that about 15,000 times. I'm actually purposefully not making a lot of splitting-related entries, because I'm hoping to be able to reduce the splitting with the Gen O.
Showing posts with label Minutae. Show all posts
Showing posts with label Minutae. Show all posts
11.7.14
Some new briefs I've been using:
Bermuda = B*ERMD
classification = KLAFGS (thanks to Mirabai)
diagnostic = DAOIGT (one of the professors says this word constantly!)
San Diego = SA*EG
stereotype = STAO*IP
incumbent = KBAENT
affiliate = FA*ELT
I always had a problem with -nic, like picnic. I just wrote it as "NIK" and defined words that needed it, but then when I wrote "picnic" my instinct would be to use N*IK or N*K, since NIK is already "nick." But N*IK is Nick, and N*K is North Carolina, so I couldn't figure out what stroke I should use for -nic. Finally yesterday I decided I had to come up with a solution. South Carolina is SO*UK, so I made NO*UK North Carolina, and now I can use N*K for -nic. I think that's going to be a much better solution, assuming I can actually remember to do it (and remember that North Carolina is NO*UK now, too).
A weird thing that happened was I changed my definition for tri- from {tri^} to {tri-^}, which would normally just have it put the hyphen in if it made a misspelled word with out it, but for some reason then I started getting "tri-angle," which was embarrassing. I defined that one as "triangle," and hopefully everything else will work properly.
I also had a crazy word come up, I think in a speech about equality: "transmogrification." Needless to say, that one was not in my dictionary yet.
Bermuda = B*ERMD
classification = KLAFGS (thanks to Mirabai)
diagnostic = DAOIGT (one of the professors says this word constantly!)
San Diego = SA*EG
stereotype = STAO*IP
incumbent = KBAENT
affiliate = FA*ELT
I always had a problem with -nic, like picnic. I just wrote it as "NIK" and defined words that needed it, but then when I wrote "picnic" my instinct would be to use N*IK or N*K, since NIK is already "nick." But N*IK is Nick, and N*K is North Carolina, so I couldn't figure out what stroke I should use for -nic. Finally yesterday I decided I had to come up with a solution. South Carolina is SO*UK, so I made NO*UK North Carolina, and now I can use N*K for -nic. I think that's going to be a much better solution, assuming I can actually remember to do it (and remember that North Carolina is NO*UK now, too).
A weird thing that happened was I changed my definition for tri- from {tri^} to {tri-^}, which would normally just have it put the hyphen in if it made a misspelled word with out it, but for some reason then I started getting "tri-angle," which was embarrassing. I defined that one as "triangle," and hopefully everything else will work properly.
I also had a crazy word come up, I think in a speech about equality: "transmogrification." Needless to say, that one was not in my dictionary yet.
10.21.14
I've always had a terrible time writing "equilibrium"; it's defined 30 ways in my dictionary, and it still comes out wrong when I write it. I noticed AB was reminding me one of the ways I have it is BR*UM. It comes up a lot in my leadership class, and I've totally memorized it now. So much easier! Another new one I use a lot is AO*LG for "algorithm." It's surprising how many different contexts that word comes up in.
I recently set my AB to remind/give me briefs for things even if it would only save one stroke. That's probably too sensitive if you're just starting out with AB, but now that I've been using it for a while, I think I'm going to like it. It's giving me lots of helpful things, and there were times before when I wasn't getting anything for words I wanted briefs for. Just today it gave me one for "annotated outline," which really saved me.
Looking that up reminded me that I couldn't figure out how to write "cedar." Luckily I fingerspelled it and got a brief for it (which I used 19 times in an hour). I just checked on what the problem was, and it's the fact that I recently changed -dar from DAR to DA*R. I was having conflicts with Darlene, Darnell, etc., and I figured it should've been DA*R all along. But it's going to take some getting used to writing it - radar is probably the first one I'll learn, although it isn't sticking yet.
A couple other items of note are that I was pleasantly surprised to stroke out "Tiananmen Square" as best I could and have it actually translate, and I successfully fingerspelled "heterogenous." I miss the asterisk in "help" sometimes, and I wind up with "hep," so I'm used to seeing and erasing "hep" quite a bit, but I finally got to actually use it the other day when someone said "hep C."
I recently set my AB to remind/give me briefs for things even if it would only save one stroke. That's probably too sensitive if you're just starting out with AB, but now that I've been using it for a while, I think I'm going to like it. It's giving me lots of helpful things, and there were times before when I wasn't getting anything for words I wanted briefs for. Just today it gave me one for "annotated outline," which really saved me.
Looking that up reminded me that I couldn't figure out how to write "cedar." Luckily I fingerspelled it and got a brief for it (which I used 19 times in an hour). I just checked on what the problem was, and it's the fact that I recently changed -dar from DAR to DA*R. I was having conflicts with Darlene, Darnell, etc., and I figured it should've been DA*R all along. But it's going to take some getting used to writing it - radar is probably the first one I'll learn, although it isn't sticking yet.
A couple other items of note are that I was pleasantly surprised to stroke out "Tiananmen Square" as best I could and have it actually translate, and I successfully fingerspelled "heterogenous." I miss the asterisk in "help" sometimes, and I wind up with "hep," so I'm used to seeing and erasing "hep" quite a bit, but I finally got to actually use it the other day when someone said "hep C."
Old Fixes
I probably haven't been doing as much dictionary maintenance as I should lately. I bet there are still a lot of word groups that I don't have defined the way I write them, but somehow I've stopped looking out for them. I even have a list of stuff to work on that I've just been completely ignoring. Maybe I feel like the mistakes don't go through that often, so it doesn't seem as important anymore. I did fix quite a few a long time ago that I've never had time to mention, though.
I changed -tal to T*AL (257 instances), changed it so words like "influential" could be written like IN/FLAOUNL (198), added /ELZ for words like novels (642), a -VS for words like conclusive = CON/KLAOUVS (416), -AIRBL for
-ational, -TAIRBL for -tational (3) and KAIRBL for -casional (306), -lize and
-mize as LAO*IZ (349) and MAO*IZ (47), GA*ET for -gate (215), NALT for -nality (78), LIFK for -listic (52), changed -sen to S*EN so it wouldn't conflict with words that started with SEN like sensationalism, and changed li- to L*EU.
I feel like my prefixes and suffixes are still all over the place. I don't have a uniform system for them. Someone told me at one point to put an asterisk in all the suffixes, so I did for a ton of them, and then I didn't like it so I took them out, but now I basically do it again, except only for words that are already words; but I'm discovering that a lot of words start with the same sound, like the sen- and -sen thing, so even though "sen" isn't a word, I should still do an asterisk in -sen just for consistency so I know what to write.
I guess I should work on that. It actually shouldn't take as much time as it used to now that I figured out how to edit dictionaries in Word.
Clean Words
Just in time for my captioning work, Jeremy put up the list of dirty words that you could add to your "words that have been deleted from the spelling dictionary" file. If you don't have a word in your spelling dictionary, the Eclipse AI won't guess it for TM, integrated pre/suf, or anything else. All you had to do was paste the list into your file, and voila. I took an extra step, though; I wanted to text global all the words as {NULL} so they couldn't even possibly be on the screen for captioning.
It would've been a laborious process doing it by hand, but thanks to some playing around that I did for the IE (it's a long story involving importing/exporting dictionaries to use special keyboard layouts, and I don't even think I needed to do it in the first place), I realized that you can export a dictionary, edit it in Word, import it, and make changes that way! So all the times that I've wished I could "find and replace" all instances of something in a dictionary, I actually could have!
I used it to put = {NULL} after all the words, and also to change them to all caps since that's how they're going to look when I'm captioning, and I instantly had dictionary entries for the entire list. And there are some really bad words on that list, so I'm glad I'm protected now.
I also realized that for captioning, you want to have a lowercase "s" with your acronyms; like if they say there were multiple DAs, you don't want that coming out as DAS; it doesn't make any sense. So as I was editing and I noticed letters next to "s," I slowly just defined them with a lock case, but eventually I actually had time to write/define them all. I hadn't missed many, and it turned out to not take that long (I probably should've just done that in the first place, but I thought it would be more time-consuming than it was).
I had 1st defined as "first," which was really annoying. I don't know how that happened, but I definitely fixed it. I've also been defining common phrases like "10 or 15," "10 to 15," and "10 and 15" with the 10 as a numeral, because otherwise it comes out as "ten or 15," and I don't think about it fast enough to use my numeral trigger before the "ten."
According to my list of things I wanted to write about, I also spent some time paying attention to getting things like YA*RD and WI*CK in my dictionary as ^yard and ^wick, but I don't remember about that anymore. Probably a good thing to do anytime I'm writing something with an asterisk, expecting it to stick, and it doesn't. Maybe I'm not seeing them anymore because I get the delete space in there instead now.
I got into the suffix spelling rules and fixed it so I can't get things like "creativetivity," "establishmentment," and "streghtenenned" anymore, too. Really you would think the AI would be smart enough not to do those in the first place. I guess I don't have those things defined properly in the pre/suf table.
It would've been a laborious process doing it by hand, but thanks to some playing around that I did for the IE (it's a long story involving importing/exporting dictionaries to use special keyboard layouts, and I don't even think I needed to do it in the first place), I realized that you can export a dictionary, edit it in Word, import it, and make changes that way! So all the times that I've wished I could "find and replace" all instances of something in a dictionary, I actually could have!
I used it to put = {NULL} after all the words, and also to change them to all caps since that's how they're going to look when I'm captioning, and I instantly had dictionary entries for the entire list. And there are some really bad words on that list, so I'm glad I'm protected now.
I also realized that for captioning, you want to have a lowercase "s" with your acronyms; like if they say there were multiple DAs, you don't want that coming out as DAS; it doesn't make any sense. So as I was editing and I noticed letters next to "s," I slowly just defined them with a lock case, but eventually I actually had time to write/define them all. I hadn't missed many, and it turned out to not take that long (I probably should've just done that in the first place, but I thought it would be more time-consuming than it was).
I had 1st defined as "first," which was really annoying. I don't know how that happened, but I definitely fixed it. I've also been defining common phrases like "10 or 15," "10 to 15," and "10 and 15" with the 10 as a numeral, because otherwise it comes out as "ten or 15," and I don't think about it fast enough to use my numeral trigger before the "ten."
According to my list of things I wanted to write about, I also spent some time paying attention to getting things like YA*RD and WI*CK in my dictionary as ^yard and ^wick, but I don't remember about that anymore. Probably a good thing to do anytime I'm writing something with an asterisk, expecting it to stick, and it doesn't. Maybe I'm not seeing them anymore because I get the delete space in there instead now.
I got into the suffix spelling rules and fixed it so I can't get things like "creativetivity," "establishmentment," and "streghtenenned" anymore, too. Really you would think the AI would be smart enough not to do those in the first place. I guess I don't have those things defined properly in the pre/suf table.
Briefs and Things
I have a couple things I've been working on, like trying not to repeat consonants. I think my theory is set up to react better, for example, to GAOI/YA/NA than GAOI/YAN/NA. It could be defined either away, but I'm trying to train myself to do it the first way, and I think TM will make better choices that way, too. It's a real problem writing things 50 different ways. Even though they're legitimate outlines, they're not in my dictionary that way yet, and they're not translating.
I've been seeing lots of areas where I can make briefs in things that get repeated frequently. For weather, they say partly cloudy/skies, mostly sunny/skies, pop-up showers, patchy fog, seven-day forecast, and hour-by-hour forecast. I've got briefs now for NBA, NCAA, NFL, and NHL. Even things that aren't specific like "umbrella" and "preliminary" seem to come up a lot.
I also finally sorted my dictionary by strokes and frequency, and I'm trying to learn briefs now for organic, especially, and invitation. Organic is sticking, and I've used it 168 times in the past 10 days.
Mostly I'm just working on getting used to the IE. I still haven't gotten it into a comfortable position. I rarely ever feel like I can just write on it. It seems like I have to really slow down and be super focused about what I'm doing, or everything comes out wrong.
I'm still having problems with the whole "one word, two words, hyphenated" thing, but that's probably something everyone has problems with. I think I'm getting better, though. When in doubt I used to just put an asterisk in the second word and hope it would work out, but I haven't been doing that as much lately. Now my go-to is just to write it as two words, and then when I edit the transcript later I figure out what it should've been and add it to my list of words to practice if it wasn't supposed to be two words. 8 out of 20 words on my list right now are from that category. The worst are the ones I can't use an asterisk to join, like shorthair.
Since the asterisk is farther away (or at least it feels that way) on the IE, I changed "we're" to WAOER. I think I've almost fully learned to do it that way instead of WAO*ER, but I keep trying to do YOUR and YAOUF and WAOEF without asterisks now, too. I guess I could change them all, but I'd really rather have WAOER be the exception.
I haven't had any luck at all learning SKP-P yet. I think I need a different method than just writing it five times a day, because that's not working at all.
I've been seeing lots of areas where I can make briefs in things that get repeated frequently. For weather, they say partly cloudy/skies, mostly sunny/skies, pop-up showers, patchy fog, seven-day forecast, and hour-by-hour forecast. I've got briefs now for NBA, NCAA, NFL, and NHL. Even things that aren't specific like "umbrella" and "preliminary" seem to come up a lot.
I also finally sorted my dictionary by strokes and frequency, and I'm trying to learn briefs now for organic, especially, and invitation. Organic is sticking, and I've used it 168 times in the past 10 days.
Mostly I'm just working on getting used to the IE. I still haven't gotten it into a comfortable position. I rarely ever feel like I can just write on it. It seems like I have to really slow down and be super focused about what I'm doing, or everything comes out wrong.
I'm still having problems with the whole "one word, two words, hyphenated" thing, but that's probably something everyone has problems with. I think I'm getting better, though. When in doubt I used to just put an asterisk in the second word and hope it would work out, but I haven't been doing that as much lately. Now my go-to is just to write it as two words, and then when I edit the transcript later I figure out what it should've been and add it to my list of words to practice if it wasn't supposed to be two words. 8 out of 20 words on my list right now are from that category. The worst are the ones I can't use an asterisk to join, like shorthair.
Since the asterisk is farther away (or at least it feels that way) on the IE, I changed "we're" to WAOER. I think I've almost fully learned to do it that way instead of WAO*ER, but I keep trying to do YOUR and YAOUF and WAOEF without asterisks now, too. I guess I could change them all, but I'd really rather have WAOER be the exception.
I haven't had any luck at all learning SKP-P yet. I think I need a different method than just writing it five times a day, because that's not working at all.
Average Semester Speed
Just for fun, I kept a record (or at least tried to) of the speed of all the jobs I wrote last semester. The fastest one, 201 wpm, was just one of the teleconferences I covered. Must have had a lot of people talking really fast on that one. It's pretty crazy how fast people like to go on those. The slowest one was my anthropology class, which clocked in at 136 wpm one day. It only had an average of 147 wpm for the whole semester, but the material was so ridiculously dense it felt like 250 some days. I never knew what words that professor was going to throw out.
My average for all jobs for the whole semester was 179 wpm. I'm not sure if that's more indicative of how fast people were actually talking, or just how fast I'm able to write material in general. Of course, I can go faster if it's easy stuff. During the last budget meeting, I was going at over 300 sometimes!
In successes and fixes news, I was pretty impressed with myself when I wrote counterinsurgencies and it came out perfectly right. I also wrote emoji, and it wasn't in my dictionary, but all the parts are individually defined, so I successfully built a word, which doesn't happen often. I fingerspelled it during the event, but it was cool to find out later when I went to put it in my dictionary that I could've just written it.
I found out that having ", eth-" defined as ", earth" was a really bad idea. It seemed like a good move when I was covering an astronomy class. They talked about the Earth a lot. Then, all of a sudden when I was doing anthropology, and they're talking about ethnographies and ethnographic and ethnological and everything you can think of that starts with "eth-," it was very bad. And that is why you should not define word parts as words.
I also fixed a couple of suffixes. I had "realitity" come out when I stroked "reality" and "-ty," so I told -ty not to attach if there's already a -ty there. I also did something similar to fix intellectualtual.
My average for all jobs for the whole semester was 179 wpm. I'm not sure if that's more indicative of how fast people were actually talking, or just how fast I'm able to write material in general. Of course, I can go faster if it's easy stuff. During the last budget meeting, I was going at over 300 sometimes!
In successes and fixes news, I was pretty impressed with myself when I wrote counterinsurgencies and it came out perfectly right. I also wrote emoji, and it wasn't in my dictionary, but all the parts are individually defined, so I successfully built a word, which doesn't happen often. I fingerspelled it during the event, but it was cool to find out later when I went to put it in my dictionary that I could've just written it.
I found out that having ", eth-" defined as ", earth" was a really bad idea. It seemed like a good move when I was covering an astronomy class. They talked about the Earth a lot. Then, all of a sudden when I was doing anthropology, and they're talking about ethnographies and ethnographic and ethnological and everything you can think of that starts with "eth-," it was very bad. And that is why you should not define word parts as words.
I also fixed a couple of suffixes. I had "realitity" come out when I stroked "reality" and "-ty," so I told -ty not to attach if there's already a -ty there. I also did something similar to fix intellectualtual.
Finessing
The only major problem I'm having with my writing right now seems to be stacking "and." I stack it with everything. People really advise against writing APBD, so I decided to change it to SKP-P. It's super easy to stroke, but the problem is I never do it, and I stack like three things with "and" on every single job. It's really annoying. Whenever I notice myself stack it, though, I'm trying to erase the mistake and force myself to write SKP-P instead. It doesn't seem to be working yet, but I remember when I felt like it was going to be absolutely impossible to write punctuation with both hands, so I guess I'll make it happen eventually.
I also randomly stroke the initial S sometimes, or maybe it's the initial and final Ss. I'm hoping that will stop with the new machine, though. And a lot of time, I'll accidentally stroke initial T when I mean to stroke S, and then I try to erase it but I stack the S and the asterisk, so I wind up with "it S." I haven't even trade to think of a plan for fixing that one. The obvious answer would be to change the definition for S*, but then I'd have to change the entire alphabet, and it seems to work all right for the most part, so I don't really want to do that. I have used things like S-PG for that alphabet before, but I seemed to get tripped up. I also get tripped up a lot with the asterisk alphabet, so maybe it doesn't matter which one I use. It is a lot easier to fingerspell when you're captioning and you don't have to worry about upper and lower case.
I'm pretty much guaranteed to stack "can you" at the beginning of a sentence, too. I haven't been able to train myself to be cognizant of that and stop doing it yet.
I found a huge issue with my awesome "speaker IDs in slop strokes" strategy. I wound up getting words like "bliss" coming up as crazy words because I had PWHREUS as a possible misstroke for TKPWHREUS. Of course, if it's something like TKPWHR-D, which could be misstroked as PWHR-D (BL-D), then it's not a problem, because I don't want that to be a word, anyway. At first I thought I would just deal with the words as they popped up, but then they started getting embarrassing. I was on air trying to write about a "fly ball," and the only way to keep it from coming out as "glioball" was to fingerspell it. Every time I wrote TPHRAOEU, it got auto-corrected to TKPWHRAOEU, which is apparently my prefix for glio-, not that I ever use it.
So I looked at the possible misstrokes, and identified anything like fl-, bl-, gr-, etc. that could actually combine with things to form a word, and then I looked at all my final bank combinations with those, and got rid of any words like fleck, Greg, etc. Then I bolded those initial combinations in my master list, and now whenever I add a secondary bank combination to the slop strokes, I check first to make sure it's not a word and get rid of it if it is. I'd rather have "fly" come out when I was going for the speaker ID for "Brian" than not be able to write fly at all.
I also randomly stroke the initial S sometimes, or maybe it's the initial and final Ss. I'm hoping that will stop with the new machine, though. And a lot of time, I'll accidentally stroke initial T when I mean to stroke S, and then I try to erase it but I stack the S and the asterisk, so I wind up with "it S." I haven't even trade to think of a plan for fixing that one. The obvious answer would be to change the definition for S*, but then I'd have to change the entire alphabet, and it seems to work all right for the most part, so I don't really want to do that. I have used things like S-PG for that alphabet before, but I seemed to get tripped up. I also get tripped up a lot with the asterisk alphabet, so maybe it doesn't matter which one I use. It is a lot easier to fingerspell when you're captioning and you don't have to worry about upper and lower case.
I'm pretty much guaranteed to stack "can you" at the beginning of a sentence, too. I haven't been able to train myself to be cognizant of that and stop doing it yet.
I found a huge issue with my awesome "speaker IDs in slop strokes" strategy. I wound up getting words like "bliss" coming up as crazy words because I had PWHREUS as a possible misstroke for TKPWHREUS. Of course, if it's something like TKPWHR-D, which could be misstroked as PWHR-D (BL-D), then it's not a problem, because I don't want that to be a word, anyway. At first I thought I would just deal with the words as they popped up, but then they started getting embarrassing. I was on air trying to write about a "fly ball," and the only way to keep it from coming out as "glioball" was to fingerspell it. Every time I wrote TPHRAOEU, it got auto-corrected to TKPWHRAOEU, which is apparently my prefix for glio-, not that I ever use it.
So I looked at the possible misstrokes, and identified anything like fl-, bl-, gr-, etc. that could actually combine with things to form a word, and then I looked at all my final bank combinations with those, and got rid of any words like fleck, Greg, etc. Then I bolded those initial combinations in my master list, and now whenever I add a secondary bank combination to the slop strokes, I check first to make sure it's not a word and get rid of it if it is. I'd rather have "fly" come out when I was going for the speaker ID for "Brian" than not be able to write fly at all.
Bits and Bobs
I've been covering a lot of techy stuff. People are always talking about Drupal, Java, Linux, servlets, HTML, RSS feeds, you name it. I feel like the fact that I know a tiny bit of HTML and tech-type stuff has helped me out. I'm always proud of myself when I get something like JSON right and think, "I bet some other CART providers wouldn't know what that is." The more teleconferences I listen to, the more wonky words I can get in there like syslog, nav, dev, etc.
Alan Peacock had a great article in the JCR about getting things like @ and # in your dictionary. I have @ in there, so that's not a problem, but I don't have anything for # yet. It never comes up in CART, but when I start captioning, it's going to be important.
I've been doing my speaker IDs as GL-[first initial of name] forever, and it was really becoming a problem when I had to do 5-30 new speaker IDs for every event, because each meeting has different speakers. The main problem was not only did I define all the IDs, I also had to define all the misstrokes for them. I thought there might be something I could do with the speaker ID table, but I wasn't really sure.
Then someone on the Eclipse FB group posted something about inflected endings and slop strokes, which was totally unrelated, but it reminded me: slop strokes! So I put all the misstrokes in as slop strokes, and now they physically *can't* come out wrong. All I have to do is define each misstroke for each initial once, and that's it! They're all set for every meeting I write after that. I'm still adding initials as they come up, but I have 36 so far.
A professor rattled off "Minneapolis, Calgary, Montreal, Toronto, Edmonton, and even Moscow" the other day, and I was pretty relieved when they all came out perfectly. I have a great brief for Minneapolis (MIPS, which goes with IPS for Indianapolis), but the rest were just in there. I stroked out "heteronormative" the way I thought it should be and that came out perfectly, too.
I've been doing a lot of stroking things out the long way and hoping that helps them translate better. Sometimes it works, sometimes it doesn't. Lots of times I think the short way was in there, but whatever crazy way I decided to do the long way didn't work. I did have to put "youse" in my dictionary the other day because it wasn't in there at all.
I turned my TM slider up to about 50%, but it was being too aggressive, so I dialed it back down to 29% based on some things I didn't want it to mess with. It does pretty well. I don't like it when it takes a word like "overly," which is just over + -ly and decides that was an untran because it wasn't in my dictionary. But that's not really a big deal.
As I go through transcripts, I still pick out words that I shouldn't have gotten wrong and add them to my practice list. It only has 12 words on it, but I'm at least that many transcripts behind on editing. I'm working on hitting "logical" with an asterisk for words like methodological and genealogical. It's really tough fingering for me, but there's got to be a distinction between "methodological" and "was the method logical."
I like to do my Phoenix speed drills every day, too. It's not even a "have to" at this point; I just like to do it. It keeps me grounded. And it's a little bit like a game. It's one way I can really see progress, and it helps me work on stuff I have problems with. I've even gotten a couple drills maxed out at 220 wpm, which is as fast as the free metronome program I use goes. I'm up to 185 wpm or higher on all the drills, and my average right now is 191 wpm.
Alan Peacock had a great article in the JCR about getting things like @ and # in your dictionary. I have @ in there, so that's not a problem, but I don't have anything for # yet. It never comes up in CART, but when I start captioning, it's going to be important.
I've been doing my speaker IDs as GL-[first initial of name] forever, and it was really becoming a problem when I had to do 5-30 new speaker IDs for every event, because each meeting has different speakers. The main problem was not only did I define all the IDs, I also had to define all the misstrokes for them. I thought there might be something I could do with the speaker ID table, but I wasn't really sure.
Then someone on the Eclipse FB group posted something about inflected endings and slop strokes, which was totally unrelated, but it reminded me: slop strokes! So I put all the misstrokes in as slop strokes, and now they physically *can't* come out wrong. All I have to do is define each misstroke for each initial once, and that's it! They're all set for every meeting I write after that. I'm still adding initials as they come up, but I have 36 so far.
A professor rattled off "Minneapolis, Calgary, Montreal, Toronto, Edmonton, and even Moscow" the other day, and I was pretty relieved when they all came out perfectly. I have a great brief for Minneapolis (MIPS, which goes with IPS for Indianapolis), but the rest were just in there. I stroked out "heteronormative" the way I thought it should be and that came out perfectly, too.
I've been doing a lot of stroking things out the long way and hoping that helps them translate better. Sometimes it works, sometimes it doesn't. Lots of times I think the short way was in there, but whatever crazy way I decided to do the long way didn't work. I did have to put "youse" in my dictionary the other day because it wasn't in there at all.
I turned my TM slider up to about 50%, but it was being too aggressive, so I dialed it back down to 29% based on some things I didn't want it to mess with. It does pretty well. I don't like it when it takes a word like "overly," which is just over + -ly and decides that was an untran because it wasn't in my dictionary. But that's not really a big deal.
As I go through transcripts, I still pick out words that I shouldn't have gotten wrong and add them to my practice list. It only has 12 words on it, but I'm at least that many transcripts behind on editing. I'm working on hitting "logical" with an asterisk for words like methodological and genealogical. It's really tough fingering for me, but there's got to be a distinction between "methodological" and "was the method logical."
I like to do my Phoenix speed drills every day, too. It's not even a "have to" at this point; I just like to do it. It keeps me grounded. And it's a little bit like a game. It's one way I can really see progress, and it helps me work on stuff I have problems with. I've even gotten a couple drills maxed out at 220 wpm, which is as fast as the free metronome program I use goes. I'm up to 185 wpm or higher on all the drills, and my average right now is 191 wpm.
Learn Your Software
I've learned some pretty cool stuff from the Eclipse FB group. I strongly recommend checking it out if you're on Eclipse. I also watched the full 8 hours of Eclipse basic training tutorials (bo-ring!). It was mostly about title pages and auto indexing and stuff I don't use, or stuff I already know how to do, but I did pick up a couple ideas.
I have a stroke that takes me to the bottom of my realtime feed/has me follow it, and it was always bad when I forgot to hit that after I scrolled up to look at something. But I found out about the "follow always" checkbox in the realtime tab, and now that's not a problem anymore.
I learned that you can make conflicts if you want a certain thing to happen after a number. I use P-KT for % and PER/KRENT for percent, but sometimes it's so much easier to hit P-KT, that I just don't get PER/KRENT in there. I think I've got it set up now that I can write "a large P-KT" or something and it will come up "a large percent," so that's cool. I've been trying to see new opportunities for conflicts overall. Sometimes I miss the F in I've (AO*IV) and get "aye," but why not make it a conflict with the first choice being "aye"? Just today I changed YO*U from ewe to \ewe\you're, because I miss that R so often.
The best idea I got from the FB group was about suffixes. I think someone just said something about their suffix rules table, and it reminded me about how I keep getting things like "organizationtion" when I accidentally drag an extra G into ORGS/S, making it ORGS/GS. So I made a rule that when the word ends in -tion, the suffix should delete the -tion and add an -s, and voila! ORGS/GS is organizations now, and I won't get orientationtion or objectiontion or anything like that, either.
I've come up with tons of applications for that now that I've realized I can do it. No more defectiveive if I already tucked the V and forgot about it (DE/F*EFKT/IV), no more passageage if I got confused and did PAJ/AJ, no more strategicically, or longerer if I didn't realize I tucked the R (LORNG/ER). I don't think -tor was in there as a real suffix; it was in my dictionary, but it wasn't in the suffix table, so it didn't have any suffix rules. I kept getting things like compacttor and reacttor because instead of RE/AK/TOR, I'd write RAEKT/TOR.
But I fixed that rule, so it works for -tor and -tors. And I was getting things like "humorral," so I told it if you're going to add -ral and the word already ends in "r," delete the first "r." I feel like someone who does realtime already has all these suffixes in their suffix table and suffix spelling rules, and I must've missed out on them in an update or something. I should ask on depoman or the FB group for someone's tables, but I'm afraid it might mess things up. I don't see how it could, though, really; it would only change the suffixes in English. It wouldn't have anything to do with my steno outlines. I guess I'd just have to make sure all the things I've changed were still in there.
I also changed my background color from white to gray. Someone on the FB group said it's easier on the eyes. I've heard stuff like that before, but I never really thought about actually changing it until I saw it there. I really do like it better.
I have a ton of different settings files I use for different companies, so it's a pain to change suffix tables or whatever in all of them. I asked about it on FB, and Dave Stanley said that I could just have a global.set that all settings would use for certain things. It seemed like a great idea, except that it overwrites your realtime settings if you let it change your translation settings. It also overwrites your job dictionaries no matter what you do, which is a drag.
I learned how to finally get TM to stop messing with my stroke for "a," which is awesome. I told it to stop pulling "an" and "everyone" into other words, too. I actually turned TM up a bit. The new sliders are kind of confusing, but I understand them now. My main problem was that TM wasn't being aggressive enough; there were tons of words it just left alone. So I unchecked "require an untran," and I bumped it up from whatever it was at (it might've been as low as 1%) to 30%, and I think it's doing better now.
I found out there's a dictionary entry you can use to reject the last AB suggestion and get a new one all at once, and I also found a macro for requesting a brief for the last word, which I think will come in handy.
I have a stroke that takes me to the bottom of my realtime feed/has me follow it, and it was always bad when I forgot to hit that after I scrolled up to look at something. But I found out about the "follow always" checkbox in the realtime tab, and now that's not a problem anymore.
I learned that you can make conflicts if you want a certain thing to happen after a number. I use P-KT for % and PER/KRENT for percent, but sometimes it's so much easier to hit P-KT, that I just don't get PER/KRENT in there. I think I've got it set up now that I can write "a large P-KT" or something and it will come up "a large percent," so that's cool. I've been trying to see new opportunities for conflicts overall. Sometimes I miss the F in I've (AO*IV) and get "aye," but why not make it a conflict with the first choice being "aye"? Just today I changed YO*U from ewe to \ewe\you're, because I miss that R so often.
The best idea I got from the FB group was about suffixes. I think someone just said something about their suffix rules table, and it reminded me about how I keep getting things like "organizationtion" when I accidentally drag an extra G into ORGS/S, making it ORGS/GS. So I made a rule that when the word ends in -tion, the suffix should delete the -tion and add an -s, and voila! ORGS/GS is organizations now, and I won't get orientationtion or objectiontion or anything like that, either.
I've come up with tons of applications for that now that I've realized I can do it. No more defectiveive if I already tucked the V and forgot about it (DE/F*EFKT/IV), no more passageage if I got confused and did PAJ/AJ, no more strategicically, or longerer if I didn't realize I tucked the R (LORNG/ER). I don't think -tor was in there as a real suffix; it was in my dictionary, but it wasn't in the suffix table, so it didn't have any suffix rules. I kept getting things like compacttor and reacttor because instead of RE/AK/TOR, I'd write RAEKT/TOR.
But I fixed that rule, so it works for -tor and -tors. And I was getting things like "humorral," so I told it if you're going to add -ral and the word already ends in "r," delete the first "r." I feel like someone who does realtime already has all these suffixes in their suffix table and suffix spelling rules, and I must've missed out on them in an update or something. I should ask on depoman or the FB group for someone's tables, but I'm afraid it might mess things up. I don't see how it could, though, really; it would only change the suffixes in English. It wouldn't have anything to do with my steno outlines. I guess I'd just have to make sure all the things I've changed were still in there.
I also changed my background color from white to gray. Someone on the FB group said it's easier on the eyes. I've heard stuff like that before, but I never really thought about actually changing it until I saw it there. I really do like it better.
I have a ton of different settings files I use for different companies, so it's a pain to change suffix tables or whatever in all of them. I asked about it on FB, and Dave Stanley said that I could just have a global.set that all settings would use for certain things. It seemed like a great idea, except that it overwrites your realtime settings if you let it change your translation settings. It also overwrites your job dictionaries no matter what you do, which is a drag.
I learned how to finally get TM to stop messing with my stroke for "a," which is awesome. I told it to stop pulling "an" and "everyone" into other words, too. I actually turned TM up a bit. The new sliders are kind of confusing, but I understand them now. My main problem was that TM wasn't being aggressive enough; there were tons of words it just left alone. So I unchecked "require an untran," and I bumped it up from whatever it was at (it might've been as low as 1%) to 30%, and I think it's doing better now.
I found out there's a dictionary entry you can use to reject the last AB suggestion and get a new one all at once, and I also found a macro for requesting a brief for the last word, which I think will come in handy.
12.7.13
I was feeling pretty confident about things after the CCP/CBC exam, and I decided I couldn't wait around anymore for my arm to feel better. I applied to about 15 CART companies trying to drum up some real work. I got promising responses from a few. It's three weeks later now, and I've only actually done any work for one, and that's only been a couple of hours. I'm hopeful about getting some classes from another next semester, but I'm not sure it'll be a full schedule.
I'm starting to have serious doubts about my ability to make a career out of CART. I don't like having downtime. I'd rather be working. Like it or not, I'm about to have an entire month off. I may actually have to invest in captioning. The good thing about that is I can start any time; it's not dependent on semester schedules.
I've been having a problem where I keep writng -fy as FAOI, even though that's "fie" and -fy should be FEU. I had SUR as Sur for some reason instead of sur-, which caused a problem somewhere, so I fixed that. I wrote that Frozen was a "prison success movie," which was just weird. I guess it's good that it translated that way, but I certainly didn't remember that I'm supposed to write "princess" as PRIN/S*ES. Maybe I should change prison to PR*IN.
Jill posted a brilliant idea on depoman. Instead of just having "-ville" and "-borough" and whatnot just attach, she has them defined to cap the previous word *and* attach to it! I updated a few pertinent entries of my own to do that, and it's totally awesome.
I also joined the Eclipse group on FB, where I've learned some great tricks. You can use ALT + S/ALT + A to add a single word to your spelling dictionary instead of having to run a spellcheck which pushes you down to the next misspelled word whether you wanted to go anywhere or not, which is a lifesaver. There's a command to bring up your steno notes if they're not showing up on a transcript.
The most important thing I saw was a reminder to upgrade to Version 6.0.0.12. I was on .9, and I don't even think I knew there was another update. If I did, I didn't know it was a stable one. I upgraded, and it turns out they fixed the auto-brief window so it works in keyboard macro output! They fixed it around the start of the semester. I *so* wish I had known that! It would've been amazing. I've got it going now, but there's only one week left in the semester.
I haven't had time for dictionary maintenence for a while, but there was a period where I was making good progress on it. I decided it made more sense for ya'll to be YAL and -ial to be Y*AL, so I changed 961 entries. I was really used to doing -ial as YAL, though, and it's not going over so well in my writing yet. -cade needed to be KA*ID to avoid conflicting with Cade, but there weren't many of those. Similarly, -tate (141 entries) got updated to TA*IT to avoid conflicting with Tate.
-gate (162) had to be GA*ET, for obvious reasons. I was writing -ality as ALT and it wasn't translating, so I did 434 of those. Latin was defined as LANT, which made sense. I'm not sure I actually even write it that way, but I updated 86 -lant entries to be LA*NT. -rate words (465) weren't working as RA*T, although I thought I fixed that already. I went ahead and did 84 -fied words as FAOID and FID, so that should work no matter which way I do it.
BER is ber-, so I updated -ber (208) as B*ER. "-zation" words (273) weren't coming out properly. I think I decided they should be fine as STKAIGS, but I defined them all as STKA*IGS for some reason. I wanted my para- prefix (232) to be PA*R, but it wasn't defined. -cate (238) wasn't working as K*AT. YOR is yore, so -ior (84) had to be Y*OR. I'd probably write yore as YOER, though, so I'm not sure I really needed to do that one.
I'm down to only 13 more problems to fix, so maybe I can get them done over winter break.
I'm starting to have serious doubts about my ability to make a career out of CART. I don't like having downtime. I'd rather be working. Like it or not, I'm about to have an entire month off. I may actually have to invest in captioning. The good thing about that is I can start any time; it's not dependent on semester schedules.
I've been having a problem where I keep writng -fy as FAOI, even though that's "fie" and -fy should be FEU. I had SUR as Sur for some reason instead of sur-, which caused a problem somewhere, so I fixed that. I wrote that Frozen was a "prison success movie," which was just weird. I guess it's good that it translated that way, but I certainly didn't remember that I'm supposed to write "princess" as PRIN/S*ES. Maybe I should change prison to PR*IN.
Jill posted a brilliant idea on depoman. Instead of just having "-ville" and "-borough" and whatnot just attach, she has them defined to cap the previous word *and* attach to it! I updated a few pertinent entries of my own to do that, and it's totally awesome.
I also joined the Eclipse group on FB, where I've learned some great tricks. You can use ALT + S/ALT + A to add a single word to your spelling dictionary instead of having to run a spellcheck which pushes you down to the next misspelled word whether you wanted to go anywhere or not, which is a lifesaver. There's a command to bring up your steno notes if they're not showing up on a transcript.
The most important thing I saw was a reminder to upgrade to Version 6.0.0.12. I was on .9, and I don't even think I knew there was another update. If I did, I didn't know it was a stable one. I upgraded, and it turns out they fixed the auto-brief window so it works in keyboard macro output! They fixed it around the start of the semester. I *so* wish I had known that! It would've been amazing. I've got it going now, but there's only one week left in the semester.
I haven't had time for dictionary maintenence for a while, but there was a period where I was making good progress on it. I decided it made more sense for ya'll to be YAL and -ial to be Y*AL, so I changed 961 entries. I was really used to doing -ial as YAL, though, and it's not going over so well in my writing yet. -cade needed to be KA*ID to avoid conflicting with Cade, but there weren't many of those. Similarly, -tate (141 entries) got updated to TA*IT to avoid conflicting with Tate.
-gate (162) had to be GA*ET, for obvious reasons. I was writing -ality as ALT and it wasn't translating, so I did 434 of those. Latin was defined as LANT, which made sense. I'm not sure I actually even write it that way, but I updated 86 -lant entries to be LA*NT. -rate words (465) weren't working as RA*T, although I thought I fixed that already. I went ahead and did 84 -fied words as FAOID and FID, so that should work no matter which way I do it.
BER is ber-, so I updated -ber (208) as B*ER. "-zation" words (273) weren't coming out properly. I think I decided they should be fine as STKAIGS, but I defined them all as STKA*IGS for some reason. I wanted my para- prefix (232) to be PA*R, but it wasn't defined. -cate (238) wasn't working as K*AT. YOR is yore, so -ior (84) had to be Y*OR. I'd probably write yore as YOER, though, so I'm not sure I really needed to do that one.
I'm down to only 13 more problems to fix, so maybe I can get them done over winter break.
10.19.13
I'm still enjoying CART, although sometimes it can be pretty boring, and I look forward to classes where the instructors say more/faster so I don't have any downtime. And sometimes I have to shower after lunch, which kind of bugs me. But I think it's worth it. I wish I had more work. I don't have any classes at all on Fridays. But I'm only working for one company, so I haven't exactly run out of options on that front yet. I'm waiting until after the CBC/CCP exam on 11/1 so I can see how I feel about that before I reach out to more companies.
I love the idea of doing remote CART exclusively, but I don't like the idea of not working during the summer. I'm not sure what else I could do during the summer, though. I guess I could do some captioning, but I'd have to buy AccuCap, which is $3k, and I'd need to have phone lines installed, and get an audio coupler and all of that stuff. I guess it would be worth it to have income during the summer, but I wish there were an easier way to get summer work.
I've been going through my dictionary maintenance list, and I've noticed a disturbing trend of finding things that I wanted to go back and fix - like "-cal" words not working when I stroked K-L - that weren't defined that way just because it was wrong to write them that way. -cal is KA*L, and K-L is -cle, so of course "magical" wasn't defined as MAG/K-L. I should probably reinforce KA*L, not define all the -cal words as K-L and KA*L. I guess it doesn't hurt to have them in there as K-L, too, where it doesn't cause any conflicts.
I think the problem is when I'm doing realtime, I just write the first thing that comes to mind, and it isn't always the right thing, even though it makes sense at the time. I don't like going through and rewriting (in the case of -cal) 580 words the wrong way, though. I'm almost reinforcing the wrong thing. I always write the the right way, too, though, just to make sure it's in there that way as well. Hopefully just by writing all those words at least some way will stick and there won't be any hestitation the next time I write them.
I'm probably supposed to do -ice words as consonant + IS, but I wrote 253 of those as IS just in case. -cept works fine as SEPT, but sometimes I do it as SE*PT, so 27 of those work now. Dis- is just DIS, but some words sound like DIZ, so I fixed about 5 of those to work that way. -ling should be L*ING, but that's hard to write and something I think I just came up with myself, so it's not ingrained at all, and lots of times I wind up stroking LG. I have that defined as -ing for misstrokes, but I fixed it so 532 of those should work as -ling now. And -ious is typically YOUS, but I fixed 670 words so that YUS works, too.
I never seem to make any progress on my dictionary maintenance list. I cross things off, but then I add more things, so it never gets any shorter. I have 19 problems to address right now. I don't always spend a lot of time working on it, though. Starting next week I have to start practicing for the CCP/CBC, so I probably won't do much with it until after the exam.
I'm still having problems where I try to put asterisks on all of my ending word parts whether they need them or not. I wish I had just left my dictionary that way after I changed it to be like that. I guess hindsight is 20/20, though. And maybe there are a lot of endings that I didn't catch and hadn't changed, so I'm not as bad off as I think I am. For now, I'm still just trying to remember which ones need asterisks and which ones don't.
I'm trying to be a little less strict with the realtime rules. I have a lot of trouble trying to remember to write devastate as DEV/STA*IT. DEV is delve, so you can't write DEV/STATE or it would be "delve state." But who's ever going to say "delve state?" Someone sometime maybe, I guess. But "delve stating," is even less likely, so I finally broke down and just defined DEV/STA*IT/G as devastating. I've been trying to think about that kind of thing more often. It goes against all the rules of realtime, so I guess I'll find out sooner or later whether it hurts or helps.
I love the idea of doing remote CART exclusively, but I don't like the idea of not working during the summer. I'm not sure what else I could do during the summer, though. I guess I could do some captioning, but I'd have to buy AccuCap, which is $3k, and I'd need to have phone lines installed, and get an audio coupler and all of that stuff. I guess it would be worth it to have income during the summer, but I wish there were an easier way to get summer work.
I've been going through my dictionary maintenance list, and I've noticed a disturbing trend of finding things that I wanted to go back and fix - like "-cal" words not working when I stroked K-L - that weren't defined that way just because it was wrong to write them that way. -cal is KA*L, and K-L is -cle, so of course "magical" wasn't defined as MAG/K-L. I should probably reinforce KA*L, not define all the -cal words as K-L and KA*L. I guess it doesn't hurt to have them in there as K-L, too, where it doesn't cause any conflicts.
I think the problem is when I'm doing realtime, I just write the first thing that comes to mind, and it isn't always the right thing, even though it makes sense at the time. I don't like going through and rewriting (in the case of -cal) 580 words the wrong way, though. I'm almost reinforcing the wrong thing. I always write the the right way, too, though, just to make sure it's in there that way as well. Hopefully just by writing all those words at least some way will stick and there won't be any hestitation the next time I write them.
I'm probably supposed to do -ice words as consonant + IS, but I wrote 253 of those as IS just in case. -cept works fine as SEPT, but sometimes I do it as SE*PT, so 27 of those work now. Dis- is just DIS, but some words sound like DIZ, so I fixed about 5 of those to work that way. -ling should be L*ING, but that's hard to write and something I think I just came up with myself, so it's not ingrained at all, and lots of times I wind up stroking LG. I have that defined as -ing for misstrokes, but I fixed it so 532 of those should work as -ling now. And -ious is typically YOUS, but I fixed 670 words so that YUS works, too.
I never seem to make any progress on my dictionary maintenance list. I cross things off, but then I add more things, so it never gets any shorter. I have 19 problems to address right now. I don't always spend a lot of time working on it, though. Starting next week I have to start practicing for the CCP/CBC, so I probably won't do much with it until after the exam.
I'm still having problems where I try to put asterisks on all of my ending word parts whether they need them or not. I wish I had just left my dictionary that way after I changed it to be like that. I guess hindsight is 20/20, though. And maybe there are a lot of endings that I didn't catch and hadn't changed, so I'm not as bad off as I think I am. For now, I'm still just trying to remember which ones need asterisks and which ones don't.
I'm trying to be a little less strict with the realtime rules. I have a lot of trouble trying to remember to write devastate as DEV/STA*IT. DEV is delve, so you can't write DEV/STATE or it would be "delve state." But who's ever going to say "delve state?" Someone sometime maybe, I guess. But "delve stating," is even less likely, so I finally broke down and just defined DEV/STA*IT/G as devastating. I've been trying to think about that kind of thing more often. It goes against all the rules of realtime, so I guess I'll find out sooner or later whether it hurts or helps.
180
I really like doing CART. It's great not having to work weird hours like I would have to for captioning. And lots of times I wind up not having to actually do anything and I still get paid, which would never happen with captioning. Something's always going to be on the air, whether it's what you did prep for or not. The only bad part is that the audio isn't always that great. But I can only work with what I've got, and so far I don't think I've missed writing anything vital because of it.
I'm always more surprised by what's in my dictionary properly than by what isn't. "Hieroglyphics" came out perfectly the other day, and I already had "Micah" in there. Who knew? I have a bunch of math symbols in, like +, -, etc., and I've even got superscript set up. Auto Brief comes in handy a lot. In one of my classes, the instructor kept saying "prepositional phrase," which I write as PREP/SIGS/NAL/FRAIS, or PREP/SILGS/FRAIS if I'm feeling really confident. Auto Brief suggested "PRO*EP," which was a whole lot easier, and I wound up using that brief 30 times just for that one session.
My arm being messed up has really slowed down my progress on the Phoenix speed drills. It's just impossible to try to build speed with any kind of accuracy at this point. But I keep plugging along anyway, and sometimes I have good days with it. I finally hit a major milestone: I've got a speed of 180 wpm or better on every drill, and my average speed is 185 wpm now. Maybe that means I can finally pass the CBC/CCP this time. I'm not going to a concert the night before specifically so I won't have any regrets about it after the test, so it had better be worth it.
I've been getting some good dictionary maintenance in. I spent a couple hours on it one day, and added 956 entries. Per is P*ER because PER is per-, so I made sure all 253 -per entries were defined with P*R. I decided VAL should be Val, so I defined 84 -val entries as VA*L. I do -in and -en both as -N, so I made sure 993 -in entries and 1524 -en will work. And I guess there was something wrong with -eous words, because they were on the list, so I wrote all 126 of those.
I'm always more surprised by what's in my dictionary properly than by what isn't. "Hieroglyphics" came out perfectly the other day, and I already had "Micah" in there. Who knew? I have a bunch of math symbols in, like +, -, etc., and I've even got superscript set up. Auto Brief comes in handy a lot. In one of my classes, the instructor kept saying "prepositional phrase," which I write as PREP/SIGS/NAL/FRAIS, or PREP/SILGS/FRAIS if I'm feeling really confident. Auto Brief suggested "PRO*EP," which was a whole lot easier, and I wound up using that brief 30 times just for that one session.
My arm being messed up has really slowed down my progress on the Phoenix speed drills. It's just impossible to try to build speed with any kind of accuracy at this point. But I keep plugging along anyway, and sometimes I have good days with it. I finally hit a major milestone: I've got a speed of 180 wpm or better on every drill, and my average speed is 185 wpm now. Maybe that means I can finally pass the CBC/CCP this time. I'm not going to a concert the night before specifically so I won't have any regrets about it after the test, so it had better be worth it.
I've been getting some good dictionary maintenance in. I spent a couple hours on it one day, and added 956 entries. Per is P*ER because PER is per-, so I made sure all 253 -per entries were defined with P*R. I decided VAL should be Val, so I defined 84 -val entries as VA*L. I do -in and -en both as -N, so I made sure 993 -in entries and 1524 -en will work. And I guess there was something wrong with -eous words, because they were on the list, so I wrote all 126 of those.
PT: So Far So Not So Good
I decided not to try the Topamax. I don't really want to mess with any more meds, especially if it's not likely they're going to help, anyway. The physical therapist recommended some posture changes (don't arch my back so much; put my shoulders back more; tilt my head down) and some exercises to do to relax my neck and chest muscles, and strengthen my upper back muscles. She did some muscle work on my neck for a couple sessions, but she said I "wasn't responding like a normal case," since that wound up not helping at all. Last time I went I saw a different practitioner, and she said I have thoracic output problems, which is making my arm go numb.
She did some stuff that made my shoulder hurt, and suggested I do nerve flossing twice a day. That was a couple days ago, and my shoulder still hurts. So, so far, all I've managed to do is add an additional problem. Go physical therapy. But I'll keep going and see how it pans out.
It's kind of tough to adjust to my new writing posture. I have good days and bad days. I have lots of weird misstrokes. I was looking at my averages for my last 5 rounds of 8 shows, though, starting back on 4/24, and it goes 98.28, 98.31, 98.40, 98.6, 98.61. So that's got to signify some kind of improvement. I've been trying to slow down and really go for accuracy, and I felt like it might be leading to more paraphrasing, or leaving out an unimportant sentence here or there, but I'm actually writing 400+ more words per show than I used to, which just seems crazy.
When I stroked out RAOE/YOE/DAI/JE/NAIR/ROE the other day, I was pretty surprised to find that it translated perfectly. Guess I've written it that way before. It's nice when things like that happen. I used to not be able to remember to write "aide" at all. It would always come out aid, without thinking. But I'm actually writing "aide" now, so that's cool.
One thing that's not so cool is I've developed a problem with coming back for -G for -ing. At least once or twice a practice session, I hit -D instead of -G. I guess it's just easier, but it really messes with the transcript. I add that word to my "words to practice" list every time I catch it, though, so hopefully that will reinforce the -G.
I also tend to write "OFT T" (of the the) a lot. I've started defining phrases that way whenever I misstroke them like that, so I decided to be proactive, and I'm going through my dictionary, finding any "the" phrases, and defining them appropriately so there won't be a double "the" if I stroke it after the phrase.
She did some stuff that made my shoulder hurt, and suggested I do nerve flossing twice a day. That was a couple days ago, and my shoulder still hurts. So, so far, all I've managed to do is add an additional problem. Go physical therapy. But I'll keep going and see how it pans out.
It's kind of tough to adjust to my new writing posture. I have good days and bad days. I have lots of weird misstrokes. I was looking at my averages for my last 5 rounds of 8 shows, though, starting back on 4/24, and it goes 98.28, 98.31, 98.40, 98.6, 98.61. So that's got to signify some kind of improvement. I've been trying to slow down and really go for accuracy, and I felt like it might be leading to more paraphrasing, or leaving out an unimportant sentence here or there, but I'm actually writing 400+ more words per show than I used to, which just seems crazy.
When I stroked out RAOE/YOE/DAI/JE/NAIR/ROE the other day, I was pretty surprised to find that it translated perfectly. Guess I've written it that way before. It's nice when things like that happen. I used to not be able to remember to write "aide" at all. It would always come out aid, without thinking. But I'm actually writing "aide" now, so that's cool.
One thing that's not so cool is I've developed a problem with coming back for -G for -ing. At least once or twice a practice session, I hit -D instead of -G. I guess it's just easier, but it really messes with the transcript. I add that word to my "words to practice" list every time I catch it, though, so hopefully that will reinforce the -G.
I also tend to write "OFT T" (of the the) a lot. I've started defining phrases that way whenever I misstroke them like that, so I decided to be proactive, and I'm going through my dictionary, finding any "the" phrases, and defining them appropriately so there won't be a double "the" if I stroke it after the phrase.
7.28.13
I struck out at the EMG test, which I guess was a good thing. The neurologist doesn't think it's carpal tunnel or a pinched nerve. He said he'd "think about it" and I should wear the wrist brace at night for three weeks and then come back and see if he came up with any new ideas. I don't think I'm going to pay to make that happen. I scheduled a PT appointment for this week, so we'll see how that goes. The neurologist also wrote me a prescription to try Topamax, but I haven't gotten it filled yet.
I've been having a good streak where I remember things that have given me trouble in the past, like TS and DZ, and remember to write them out in two strokes during realtime practice. I'm doing the same thing with words that are conflicts the "normal" way I would think to write them; nothing as simple as plague/playing, but that's the idea. I just have a general feeling that I shouldn't write it the easy way. I don't remember why right then, but it pays off. Before I would just kind of be stubborn about it and write it the easy way anyway, and then have to scramble to try to fix it.
I've had a small epiphany (can that be a thing?) about numbers, too, and I'm writing them one at a time more instead of garbling them. 12 is *really* difficult for me to write with my hand the way it is, and I realized I can just write it in two strokes, with much less chance of misstroking it.
I got Pyongyang right twice during practice today (without getting it wrong, to boot). I write it out a long way: PAOE/YONG/YANG. It's hard to start. It's almost like I want to bolt whenever I have to write it. But it's not so bad once I actually do it. I also fingerspelled a lot of names in practice today; some I knew right away weren't in there and fingerspelled the whole thing, like Lindy Boggs. Others I tried to do first (Pedro Vargas) and wound up fingerspelling them after they didn't come out right. I always do a thing where I think "I have -da defined, so I can just write Brunda, that'll come out fine."
My writing is really stilted with my hand being messed up, though. I wind up with a lot of dashes in the transcript that aren't preceeded by any mistakes. I just get lost and things start to feel wrong and I might hit one wrong letter and erase it, and then dash. At least I can pull it together and do it without dropping anything. Sometimes I don't catch the mistakes, though, and I wind up just hitting an S before writing SRAR, or hitting an N after writing something with N in it. I've got an average of 98.56% accuracy for my last five practice shows, though, so I'm keeping it together pretty well.
Words that end in -nal weren't coming out right, even though I don't think I've changed anything from theory (I just do NAL), so I re-wrote all 472 of those. I also wanted to start doing -tary with an asterisk to avoid any conflicts with tear, so I fixed 145 of those entries.
I've been having a good streak where I remember things that have given me trouble in the past, like TS and DZ, and remember to write them out in two strokes during realtime practice. I'm doing the same thing with words that are conflicts the "normal" way I would think to write them; nothing as simple as plague/playing, but that's the idea. I just have a general feeling that I shouldn't write it the easy way. I don't remember why right then, but it pays off. Before I would just kind of be stubborn about it and write it the easy way anyway, and then have to scramble to try to fix it.
I've had a small epiphany (can that be a thing?) about numbers, too, and I'm writing them one at a time more instead of garbling them. 12 is *really* difficult for me to write with my hand the way it is, and I realized I can just write it in two strokes, with much less chance of misstroking it.
I got Pyongyang right twice during practice today (without getting it wrong, to boot). I write it out a long way: PAOE/YONG/YANG. It's hard to start. It's almost like I want to bolt whenever I have to write it. But it's not so bad once I actually do it. I also fingerspelled a lot of names in practice today; some I knew right away weren't in there and fingerspelled the whole thing, like Lindy Boggs. Others I tried to do first (Pedro Vargas) and wound up fingerspelling them after they didn't come out right. I always do a thing where I think "I have -da defined, so I can just write Brunda, that'll come out fine."
My writing is really stilted with my hand being messed up, though. I wind up with a lot of dashes in the transcript that aren't preceeded by any mistakes. I just get lost and things start to feel wrong and I might hit one wrong letter and erase it, and then dash. At least I can pull it together and do it without dropping anything. Sometimes I don't catch the mistakes, though, and I wind up just hitting an S before writing SRAR, or hitting an N after writing something with N in it. I've got an average of 98.56% accuracy for my last five practice shows, though, so I'm keeping it together pretty well.
Words that end in -nal weren't coming out right, even though I don't think I've changed anything from theory (I just do NAL), so I re-wrote all 472 of those. I also wanted to start doing -tary with an asterisk to avoid any conflicts with tear, so I fixed 145 of those entries.
7.21.13
I did wind up calling the doctor about my arm, because it was really starting to be a problem. I got the runaround for a few days, and then they suggested I stop taking gabapentin and try Elavil. The first day I tried it was a disaster; the pain was so bad I went back to gabapentin right away. But after a week of that I was right back where I started before I took anything at all, and I decided to give the Elavil another shot.
Today was my fourth day taking it. Saturdays are usually my day off steno practice, so that could have something to do with it, but it finally felt a *little* bit better today during practice. I go in for the EMG test on Thursday, and find out the results the Monday after that, so I've got another week of painful practice at the least.
My accuracy was consistently above 98.5 for about five shows, but then the pain started getting worse. Friday it was at 97.5, and today was good but I had a drop that invalidated the results. I don't count shows with drops in my averages. There always seems to come a point during anything I'm writing where I get overwhelmed, and I feel like I can't do it, and I want to give up. I usually wind up dropping a sentence, or half a sentence, during that time, but I'm working to push through it and just keep going instead.
I'm still struggling to catch onto the benefit of fingerspelling instead of just blindly stroking things out. It elimates having to think about the words, it's faster, and it's more accurate, but it's hard to train myself to do. I did get "Laudenberg" out perfectly just stroking it out the other day, so that was cool. But it's the exception, not the rule. I also wrote "helicopters" has "helihopters" and TM tanslated that as "hell hospitallers," which I found amusing.
The longer I go without going through my theory book, the more muddled my theory becomes. I find myself just blindly stroking things and hoping they come out right instead of remembering what I'm actually supposed to be stroking. I realized three of the briefs on my practice list were so hard to write because I was writing them incorrectly.
Today was my fourth day taking it. Saturdays are usually my day off steno practice, so that could have something to do with it, but it finally felt a *little* bit better today during practice. I go in for the EMG test on Thursday, and find out the results the Monday after that, so I've got another week of painful practice at the least.
My accuracy was consistently above 98.5 for about five shows, but then the pain started getting worse. Friday it was at 97.5, and today was good but I had a drop that invalidated the results. I don't count shows with drops in my averages. There always seems to come a point during anything I'm writing where I get overwhelmed, and I feel like I can't do it, and I want to give up. I usually wind up dropping a sentence, or half a sentence, during that time, but I'm working to push through it and just keep going instead.
I'm still struggling to catch onto the benefit of fingerspelling instead of just blindly stroking things out. It elimates having to think about the words, it's faster, and it's more accurate, but it's hard to train myself to do. I did get "Laudenberg" out perfectly just stroking it out the other day, so that was cool. But it's the exception, not the rule. I also wrote "helicopters" has "helihopters" and TM tanslated that as "hell hospitallers," which I found amusing.
The longer I go without going through my theory book, the more muddled my theory becomes. I find myself just blindly stroking things and hoping they come out right instead of remembering what I'm actually supposed to be stroking. I realized three of the briefs on my practice list were so hard to write because I was writing them incorrectly.
I had NALGS for national, which should've just been NARBL (NASHL). Nation is NAGS or NAIGS, but that doesn't really translate to national. I was trying to smush RB (PRAOERBGS) into "appreciation," I guess because it has a similar sound to precious, gracious, etc. which I write as RBS. It's not necessary, though, and it's a lot easier to just write PRAOEGS than worry about what fingers are supposed to be where on that bank. And I was also doing deposit as SDPOZ because of words like disappoint, destroy, etc. which start with SD. It's not necessary at all, though. DPOZ works just fine. It's a good thing I review takes and make note of things that are hard to write; sometimes they're only hard because I've been trying to write them incorrectly.
I decided I should write all consonant + ize endings with an asterisk, which the AI couldn't figure out at all, so I went through and re-wrote all 720 entries that end in -ize, consonant + or not. I also decided there was no reason not to end words in -IT, so I updated 488 of those entries; and I made sure all 161 -ca entries work properly with C*A.
Subscribe to:
Posts (Atom)