Return to Video

blip.tv/.../Gloriajw-PloverThoughtToTextAt240WPM351.mp4

  • 0:00 - 0:07
    This is a talk about Plover,
    the world's first Open Source steno software.
  • 0:07 - 0:13
    The steno machine, in its current form,
    was invented somewhere around 1913.
  • 0:13 - 0:17
    It's a phonetic-mnemonic chording system,
  • 0:17 - 0:20
    which means basically that everything you write
  • 0:20 - 0:26
    is tied to a lexicon of anywhere
    between 100,000 and 200,000 words --
  • 0:26 - 0:30
    some of which are completely phonetic words,
  • 0:30 - 0:35
    some of which are sort of arbitrarily
    determined by the stenographer.
  • 0:35 - 0:38
    So each stenographer has their own
    individual dictionary,
  • 0:38 - 0:43
    which can vary greatly in its content and form.
  • 0:43 - 0:45
    Steno is still --
  • 0:45 - 0:48
    even though it was originally invented in 1913
    and hasn't really been improved,
  • 0:48 - 0:50
    except that it's now computer-compatible,
  • 0:50 - 0:52
    ever since the 80's --
  • 0:52 - 0:56
    steno is still the fastest text input method that there is.
  • 0:56 - 0:58
    Speech-recognition doesn't touch it.
  • 1:00 - 1:01
    Dvorak...
  • 1:01 - 1:06
    Is kind of a joke, in comparison.
  • 1:06 - 1:14
    Professional stenographers regularly write at speeds up to anywhere between 200 and 240 words per minute.
  • 1:14 - 1:17
    That's considered the mark of a good stenographer.
  • 1:17 - 1:19
    But the world record, as you can see,
  • 1:19 - 1:23
    is 360 words per minute, at 97% accuracy.
  • 1:23 - 1:24
    I can't do that.
  • 1:24 - 1:26
    But maybe some of you will, someday.
  • 1:26 - 1:28
    Who knows?
  • 1:30 - 1:33
    Just because geeks like knowing
    the nuts and bolts of things,
  • 1:33 - 1:38
    I figured I'd give you a brief intro of how it works,
    before I tell you why you care.
  • 1:38 - 1:42
    The left hand handles the initial consonants
    of each syllable.
  • 1:42 - 1:45
    The right hand handles the ending
    consonants of each syllable.
  • 1:45 - 1:47
    And the thumbs handle the vowels.
  • 1:47 - 1:50
    So, for example, if you wanted to write the word "gauge,"
  • 1:50 - 1:54
    you do the chord that makes up G on the left hand,
  • 1:54 - 1:58
    the chord that makes up the J sound -- because it's not orthographic; it's phonetic --
  • 1:58 - 2:00
    on the right hand.
  • 2:00 - 2:02
    And then the long A sound,
  • 2:02 - 2:06
    which is a chord made up of several vowels with the thumbs.
  • 2:06 - 2:09
    So together you get TKPW: G,
  • 2:09 - 2:11
    AEU: A,
  • 2:11 - 2:14
    and PBLG: J.
  • 2:14 - 2:16
    Put it together, you get "gauge."
  • 2:16 - 2:18
    It's pretty simple.
  • 2:18 - 2:22
    And you can, like I said --
    you have many of these strictly phonetic words
  • 2:22 - 2:27
    that just are written exactly as they sound in English,
  • 2:27 - 2:31
    and then you have many, many more words, phrases, combinations of words
  • 2:31 - 2:34
    that are determined by the stenographer,
  • 2:34 - 2:37
    out of their own head.
  • 2:37 - 2:40
    So why do we need Open Source steno?
  • 2:40 - 2:45
    Steno has been a locked-up industry since the beginning,
  • 2:45 - 2:49
    but especially since the advent of computer-compatible steno machines.
  • 2:49 - 2:53
    You know, there's a single company
    with a stranglehold on the market.
  • 2:53 - 2:55
    There are a handful of other companies.
  • 2:55 - 3:00
    And they all just charge egregious prices
    for bloated software
  • 3:00 - 3:04
    that breaks all the time and has horrible DRM
  • 3:04 - 3:07
    and is completely inaccessible to people
  • 3:07 - 3:08
    who aren't professional stenographers.
  • 3:08 - 3:09
    Yes?
  • 3:09 - 3:11
    >> Do they only run on Windows, by any chance?
  • 3:11 - 3:12
    Yes, indeed.
  • 3:12 - 3:18
    Well, I think some people have got it running using, like, Windows Bootcamp or whatever, within Macs.
  • 3:18 - 3:22
    But certainly there's no proprietary steno software
    that runs on Linux.
  • 3:22 - 3:24
    I think some of it still runs on DOS, if that helps!
  • 3:24 - 3:28
    I still know some working stenographers
    who run DOS software.
  • 3:28 - 3:30
    But yeah.
  • 3:30 - 3:31
    It's a hidebound system.
  • 3:31 - 3:32
    It's locked in.
  • 3:32 - 3:34
    It's expensive as hell.
  • 3:34 - 3:39
    And that's why no one uses this incredible technology
    for anything except making a living,
  • 3:39 - 3:40
    which is a real shame.
  • 3:40 - 3:44
    So I discovered...
  • 3:44 - 3:46
    Well, I wanted to do Open Source steno for a long time,
  • 3:46 - 3:48
    because I was so frustrated with my software,
  • 3:48 - 3:50
    and because we're a shrinking industry,
  • 3:50 - 3:52
    and I want to bring more people into the field.
  • 3:52 - 3:54
    And because it's cool, and I like geeking out about it.
  • 3:54 - 4:02
    But when I realized that Microsoft
    was making a gaming keyboard
  • 4:02 - 4:05
    that had full n-key rollover, and priced at $45,
  • 4:05 - 4:08
    I realized that's basically a steno machine.
  • 4:08 - 4:09
    You know?
  • 4:09 - 4:12
    A really, really cheap, easily available steno machine.
  • 4:12 - 4:13
    Yeah?
  • 4:13 - 4:15
    >> What is n-key rollover?
  • 4:15 - 4:16
    Oh, sorry.
  • 4:16 - 4:24
    N-key rollover means that every keystroke is registered when pressed on the qwerty keyboard,
  • 4:24 - 4:26
    even if it's several keystrokes at a time.
  • 4:26 - 4:30
    So, you know, most keyboards, the typical keyboards --
  • 4:30 - 4:34
    anywhere more than three or four keys pressed at a time,
  • 4:34 - 4:36
    some of those aren't going to register.
  • 4:36 - 4:40
    But the specialty gaming keyboards make sure that everything you press registers,
  • 4:40 - 4:46
    which means that you can type steno chords
    of up to 22 keys at a time,
  • 4:46 - 4:48
    and they're all captured and noted.
  • 4:48 - 4:50
    So...
  • 4:50 - 4:51
    Yeah.
  • 4:51 - 4:53
    Steno software, $4,000.
  • 4:53 - 4:54
    Plover, totally free.
  • 4:54 - 4:57
    Plover, $45 keyboard.
  • 4:57 - 5:01
    And now I have to convince you guys that you actually care.
  • 5:01 - 5:02
    Oh, sorry.
  • 5:02 - 5:06
    Just really briefly I'll tell you how Plover got rolling.
  • 5:06 - 5:10
    Josh Lifton was working at a co-op in Brooklyn.
  • 5:10 - 5:13
    He's a freelance Python programmer.
  • 5:13 - 5:14
    I'm a freelance stenographer.
  • 5:14 - 5:20
    We both rented office space, and I told him
    that I needed a tutor, a Python tutor.
  • 5:20 - 5:23
    Because I originally wanted to write this on my own,
  • 5:23 - 5:25
    having very little Python knowledge whatsoever.
  • 5:25 - 5:27
    But I posted something in the elevator.
  • 5:27 - 5:29
    We got in touch.
  • 5:29 - 5:32
    And at first he started off giving me lessons,
  • 5:32 - 5:34
    and then as he got more excited about the project,
  • 5:34 - 5:37
    he started donating a lot of his time.
  • 5:37 - 5:38
    I mean, I paid him as much as I could.
  • 5:38 - 5:42
    I've put about $3,000 into Plover out of my own pocket.
  • 5:42 - 5:45
    But he's also donated countless hours of programming time
  • 5:45 - 5:47
    to get it where it is right now.
  • 5:47 - 5:51
    And he's kind of as hooked on steno as I am now.
  • 5:51 - 5:54
    So it's Open Source in the sense that all the code is online.
  • 5:54 - 5:58
    But it's not really community-developed at this point.
  • 5:58 - 6:01
    He's basically the only one who's contributed
    a significant amount of code.
  • 6:01 - 6:03
    But we hope that that will change.
  • 6:03 - 6:04
    Okay.
  • 6:04 - 6:06
    Why do you care?
  • 6:06 - 6:11
    You coders, with your katanas and your VR glasses in your virtual reality parlors.
  • 6:11 - 6:12
    You know?
  • 6:12 - 6:17
    What possible connection would you have with this sweet, smiling, middle-aged lady
  • 6:17 - 6:20
    in the courtroom with the paper hanging
    out of her steno machine?
  • 6:20 - 6:21
    You know, why...
  • 6:21 - 6:24
    There's nothing cyberpunk about steno.
  • 6:24 - 6:25
    I mean, it's barely even steampunk.
  • 6:25 - 6:26
    It's basically...
  • 6:26 - 6:29
    A lot of people consider it, you know...
  • 6:29 - 6:32
    Clerical, obsolete office equipment, right?
  • 6:32 - 6:36
    Sometimes I tell people, "I can write 240 words a minute!"
  • 6:36 - 6:40
    And they're like, "I only think at, like, 80, tops."
  • 6:40 - 6:45
    And I'm like, "Yeah, I don't think that's necessarily true."
  • 6:45 - 6:50
    This is an abstract of a six-part series
    that I've written on the Plover blog.
  • 6:50 - 6:54
    Six essays dealing with what steno is actually useful for.
  • 6:54 - 6:59
    I won't go through all of them in detail,
    because some of them are probably
  • 6:59 - 7:01
    more relevant to you than others.
  • 7:01 - 7:04
    But just to give a quick rundown of each one.
  • 7:04 - 7:07
    Now, you can see speed is basically at the bottom.
  • 7:07 - 7:11
    I tried to list these in order of priority for programmers.
  • 7:11 - 7:13
    Speed isn't the most important thing, you know?
  • 7:13 - 7:15
    It's useful for bragging rights.
  • 7:15 - 7:18
    For winning online typing games.
  • 7:18 - 7:22
    You know, it can be very useful
    in some specific circumstances.
  • 7:22 - 7:26
    But primarily what I think steno would be very useful for,
  • 7:26 - 7:31
    for programmers, is the fluency
    that it lends to thought when composing text.
  • 7:31 - 7:34
    Because you're thinking in discrete chunks.
  • 7:34 - 7:36
    You're generally thinking in words.
  • 7:36 - 7:39
    Or in, you know, commands with various syntax attached.
  • 7:39 - 7:43
    But they're usually, in your mind,
    probably reflected syllabically.
  • 7:43 - 7:45
    You're saying them to yourself in your head.
  • 7:45 - 7:47
    You're not spelling out every letter as you think of them.
  • 7:47 - 7:50
    When you're writing this stuff in qwerty,
  • 7:50 - 7:54
    you have to translate every letter into a finger action.
  • 7:54 - 7:55
    You know?
  • 7:55 - 7:57
    Which then you have to duplicate correctly on the keyboard.
  • 7:57 - 7:59
    Your fingers fall all over themselves,
  • 7:59 - 8:00
    you have to slow down,
  • 8:00 - 8:05
    the error correction has to happen
    once per letter instead of once per word.
  • 8:05 - 8:10
    It's far too granular, you know?
  • 8:10 - 8:13
    With steno, you're thinking in discrete words,
  • 8:13 - 8:15
    and you're writing those words as you think them.
  • 8:15 - 8:17
    And I have not used Plover for programming,
  • 8:17 - 8:20
    because, like I said, I'm still a novice.
  • 8:20 - 8:22
    But I...
  • 8:22 - 8:24
    Do any of you know NaNoWriMo?
  • 8:24 - 8:29
    The National Novel Writing Month, where you have to write
    a novel of 50,000 words in 30 days?
  • 8:29 - 8:31
    I did that a couple of times.
  • 8:31 - 8:32
    I did it once qwerty-style.
  • 8:32 - 8:34
    And once steno-style.
  • 8:34 - 8:38
    The qwerty was pure torture, because I was
    second-guessing myself at every word.
  • 8:38 - 8:42
    The steno just, like, flew out of my fingers.
  • 8:42 - 8:46
    It wasn't a good novel,
    but it was so easy to write, because it just...
  • 8:46 - 8:52
    You know, by the time my thoughts came out of my mind,
    they were already on the screen.
  • 8:52 - 8:55
    I didn't have to spend that buffer zone tip-tapping them out.
  • 8:55 - 8:56
    And I'm a fast qwerty typist.
  • 8:56 - 8:58
    I can type around 100 words per minute.
  • 8:58 - 9:00
    But I think people who think
  • 9:00 - 9:01
    that they don't think faster than that
  • 9:01 - 9:04
    don't realize how much their fingers are slowing them down.
  • 9:04 - 9:06
    Yes?
  • 9:06 - 9:10
    >> Have you spoken to any coders, or do you know any coders that are actually using steno now?
  • 9:10 - 9:16
    No, the most advance interest that I've gotten
    does seem to be from coders.
  • 9:16 - 9:19
    I think probably because Plover is Linux-only at this point,
  • 9:19 - 9:23
    and so it's mostly tech geeks who are able to use it.
  • 9:23 - 9:27
    I don't think there's anyone
  • 9:27 - 9:29
    actually using it for coding right now.
  • 9:29 - 9:32
    But I know of a couple people teaching themselves steno,
  • 9:32 - 9:34
    in order to use it to code eventually, so...
  • 9:34 - 9:39
    >>I guess maybe the closest analogy
    I might be able to make is that if you're captioning
  • 9:39 - 9:45
    a physics or statistics class, it's very punctuation-heavy.
  • 9:45 - 9:46
    Right, yeah.
  • 9:46 - 9:48
    Steno's great at punctuation.
  • 9:48 - 9:54
    >> So is it something where you basically just end up creating your own macros around programming constructs?
  • 9:54 - 9:55
    That is what steno is all about.
  • 9:55 - 9:58
    We call them defining entries in our dictionary.
  • 9:58 - 10:01
    But it's very easy to do, and very useful.
  • 10:01 - 10:06
    So I've been doing Python the Hard Way
    through CodeLesson online,
  • 10:06 - 10:09
    and this is one of our exercises we had to do.
  • 10:09 - 10:12
    A Zork-style text adventure.
  • 10:12 - 10:15
    So I took a chunk of the code that I wrote
    and totaled up the keystrokes.
  • 10:15 - 10:17
    I actually did write it on a qwerty laptop.
  • 10:17 - 10:21
    So I totaled up the keystrokes that it took me
    to write on the qwerty laptop.
  • 10:21 - 10:23
    222.
  • 10:23 - 10:25
    Then I counted as if I had done it in steno.
  • 10:25 - 10:31
    I got 119, but that's only assuming that I defined spawn_creche, that variable,
  • 10:31 - 10:34
    as a single-stroke entry.
  • 10:34 - 10:36
    So every time you reference it after that,
  • 10:36 - 10:37
    you can just write it in one stroke.
  • 10:37 - 10:39
    And the same thing with infinite_library.
  • 10:39 - 10:44
    If I'd thought that I was only gonna use those variables once or twice, I would have just written them out letter by letter.
  • 10:44 - 10:49
    And so then it would have only been 102 keystrokes,
  • 10:49 - 10:50
    rather than 119.
  • 10:50 - 10:54
    So you can see there is a really
    drastic increase in efficiency.
  • 10:54 - 10:57
    Both ergonomically, as I'll address later,
  • 10:57 - 11:03
    but also in terms of the number of potential errors
    you'll make, how far ahead of yourself you are
  • 11:03 - 11:05
    when you start discovering those errors,
  • 11:05 - 11:07
    and have to backspace back to fix them.
  • 11:07 - 11:09
    And in just...
  • 11:09 - 11:11
    When you think print, it comes out as "print";
  • 11:11 - 11:14
    it doesn't come out as P-R-I-N-T.
  • 11:14 - 11:19
    It's hard to explain how much
    of a difference this makes until you use it.
  • 11:19 - 11:22
    But I would advise everyone, if you're interested,
  • 11:22 - 11:26
    to give it a try and to see how it works out.
  • 11:26 - 11:29
    So the other thing...
  • 11:29 - 11:31
    Let's see -- how much time do I have left?
  • 11:31 - 11:32
    A fair amount.
  • 11:32 - 11:34
    So I can go through a few of these.
  • 11:34 - 11:36
    Mobile computing is, of course,
  • 11:36 - 11:39
    every cyberpunk fan's dream.
  • 11:39 - 11:40
    I was a science fiction nerd.
  • 11:40 - 11:42
    I'm still a science fiction nerd.
  • 11:42 - 11:47
    And I would desperately love to be able to walk around
    and write down all my thoughts silently,
  • 11:47 - 11:50
    and, you know, have my glasses, and...
  • 11:50 - 11:55
    Honestly, the biggest barrier here is that
    there is no commercially available
  • 11:55 - 11:58
    heads-up display for mobile computing.
  • 11:58 - 12:01
    But once there is, steno is definitely the way to go with that.
  • 12:01 - 12:04
    Because can you imagine putting a qwerty keyboard, like,
  • 12:04 - 12:09
    in a wearable-style keyboard that you're walking around with, with 112 letters or something?
  • 12:09 - 12:11
    I mean, it's just ridiculous.
  • 12:11 - 12:15
    You know, the great thing about steno
    is it's designed for the human hand.
  • 12:15 - 12:17
    It's only got 22 keys, and they're in columns.
  • 12:17 - 12:18
    And not staggered columns.
  • 12:18 - 12:20
    They're in nice aligned columns.
  • 12:20 - 12:23
    So the footprint is basically the size of your hand.
  • 12:23 - 12:27
    Any surface you can write on
    that you can put your hands on, you can steno on.
  • 12:27 - 12:29
    You know?
  • 12:29 - 12:34
    So I think there's a huge potential in mobile computing,
    once that gets going.
  • 12:34 - 12:37
    It's geeky, but in certain situations, very useful.
  • 12:37 - 12:40
    And pretty cool.
  • 12:40 - 12:41
    Accessibility.
  • 12:41 - 12:48
    Now this -- I'll talk about what I do professionally
    very briefly in the last entry point.
  • 12:48 - 12:51
    And that's transcribing for the Deaf and hard of hearing.
  • 12:51 - 12:54
    But when I talk about accessibility here,
  • 12:54 - 12:57
    I'm mainly talking about text-to-speech,
  • 12:57 - 12:59
    as opposed to speech-to-text.
  • 12:59 - 13:02
    There are a lot of people with speech disabilities.
  • 13:02 - 13:06
    Roger Ebert, who had to have his jaw
    removed because of cancer.
  • 13:06 - 13:08
    There's a kid in Ireland
    who was born without a lower jaw.
  • 13:08 - 13:14
    There are many people with various
    autistic spectrum conditions, you know,
  • 13:14 - 13:18
    who don't speak verbally, but are very fluent in text.
  • 13:18 - 13:24
    And, of course, people with hearing loss
    don't always use their voices to speak,
  • 13:24 - 13:28
    but are perfectly able to converse at speed in text.
  • 13:28 - 13:32
    Qwerty slows down their communication.
  • 13:32 - 13:33
    It's very labor-intensive.
  • 13:33 - 13:37
    It prevents, you know, easy back and forth conversations.
  • 13:37 - 13:41
    Steno is the only technology that allows you to write
    as quickly as everyone else speaks,
  • 13:41 - 13:48
    which means that if someone with a speech disability learns steno, they're able to basically converse with everyone
  • 13:48 - 13:50
    as much as they want,
  • 13:50 - 13:54
    on par with everyone else, speed-wise.
  • 13:54 - 13:57
    And, conversely, the more geeks learn steno,
  • 13:57 - 14:01
    the more Hearing geeks
    are able to converse with Deaf geeks.
  • 14:01 - 14:04
    If they don't necessarily know Sign Language,
  • 14:04 - 14:07
    they can all speak in the common language of English text.
  • 14:07 - 14:10
    So there are a lot of potentials there.
  • 14:10 - 14:12
    Ergonomics.
  • 14:12 - 14:16
    I think a big deal for a lot of people
    who work with text for a living.
  • 14:16 - 14:20
    RSIs are no joke.
  • 14:20 - 14:27
    And the individual finger motions of qwerty typing is very stressful on the muscles and tendons.
  • 14:27 - 14:31
    Each finger basically has to depress each key.
  • 14:31 - 14:34
    And you're constantly wiggling your fingers.
  • 14:34 - 14:35
    There's not much call for rest.
  • 14:35 - 14:37
    The motions that you use when writing steno...
  • 14:37 - 14:42
    First of all, the force comes
    from the forearm rather than the fingers.
  • 14:42 - 14:45
    Second of all, you're writing many fewer strokes per minute.
  • 14:45 - 14:52
    You know, this rate of speed
    is around 200 words per minute.
  • 14:52 - 14:54
    Moving your fingers like this.
  • 14:54 - 14:57
    In qwerty, you have to go like that for just 100.
  • 15:00 - 15:02
    It's also...
  • 15:02 - 15:08
    Because of the small footprint,
    you're able to use different configurations.
  • 15:08 - 15:11
    This is an ergonomic machine that I find very useful.
  • 15:11 - 15:16
    I had developing RSIs several years ago,
  • 15:16 - 15:18
    before I started steno.
  • 15:18 - 15:19
    And since I got this machine,
  • 15:19 - 15:20
    they've pretty much gone away,
  • 15:20 - 15:22
    which is really good for what I do.
  • 15:22 - 15:25
    I know a lot of programmers face that problem as well.
  • 15:25 - 15:26
    >> Wait, you had what?
  • 15:26 - 15:29
    Oh, I'm sorry -- repetitive stress injuries.
  • 15:29 - 15:30
    Yes, sorry.
  • 15:30 - 15:31
    RSIs.
  • 15:31 - 15:33
    Any typist has the potential to develop these,
  • 15:33 - 15:37
    and they can be really career-killing conditions.
  • 15:37 - 15:40
    And it's also just so much less effort, you know?
  • 15:40 - 15:45
    I can sit back and write for seven hours
    at 180 words per minute, and not break a sweat.
  • 15:45 - 15:49
    You know, whenever I try to keep up with qwerty,
  • 15:49 - 15:55
    and I'm typing 100 words a minute,
    by the end of it, I'm just... I'm wiped out.
  • 15:55 - 15:57
    It's really exhausting.
  • 15:57 - 15:58
    You wouldn't think, but it is.
  • 15:58 - 16:01
    Pure speed I already addressed.
  • 16:01 - 16:02
    It's just bragging rights, basically.
  • 16:02 - 16:04
    And then professional stenography,
  • 16:04 - 16:08
    which is honestly the main reason why I'm putting my own money and effort into developing this.
  • 16:08 - 16:12
    I'm reaching out to you guys, because you're all geeks,
  • 16:12 - 16:14
    and you probably won't become professional stenographers.
  • 16:14 - 16:21
    But you might become the ones to give steno cachet.
  • 16:21 - 16:23
    You know, you might start using it.
  • 16:23 - 16:25
    Make other people aware of it.
  • 16:25 - 16:32
    People will start playing the video games
    that you guys use to burn off stress.
  • 16:32 - 16:38
    Or to develop the steno skills
    that you will then later use for coding purposes.
  • 16:38 - 16:42
    And some people will realize
    that they actually really love doing this.
  • 16:42 - 16:43
    I love it.
  • 16:43 - 16:44
    My job --
  • 16:44 - 16:47
    I make about six figures a year.
  • 16:47 - 16:48
    I'm my own boss.
  • 16:48 - 16:55
    I sit in college classes and transcribe lectures
    all day in so many different subjects.
  • 16:55 - 17:00
    You know, from pharmacy to medical school,
    tax law, art school, you name it.
  • 17:00 - 17:01
    It's paradise.
  • 17:01 - 17:05
    And I get to, like, help people get an education.
  • 17:05 - 17:10
    There are so few of us in this city that I've been killing myself
  • 17:10 - 17:13
    trying to find coverage for the demand this semester.
  • 17:13 - 17:19
    And if I don't get more people into our profession,
    it's going to wither up and die.
  • 17:19 - 17:23
    And a lot of people who need what I do
    won't be able to get what they need.
  • 17:23 - 17:28
    So I'm hoping that by bringing steno first to the subculture,
  • 17:28 - 17:29
    and eventually to the mainstream,
  • 17:29 - 17:32
    I'll build a group of amateurs,
  • 17:32 - 17:35
    some of whom will be interested enough
  • 17:35 - 17:36
    and committed enough
  • 17:36 - 17:38
    to want to develop their skills and make it into a profession.
  • 17:38 - 17:41
    So if you know anyone who might be
    interested in doing what I do,
  • 17:41 - 17:43
    contact me after the lecture,
  • 17:43 - 17:47
    because I would definitely love to speak to them.
  • 17:49 - 17:52
    Okay, so here's my master plan for making this happen.
  • 17:52 - 17:54
    Plover currently exists.
  • 17:54 - 17:56
    It's pretty good.
  • 17:56 - 17:58
    It's Linux-only.
  • 17:58 - 18:00
    It's intended to be a keyboard emulator.
  • 18:00 - 18:04
    You know, as opposed to all of the existing proprietary software out there,
  • 18:04 - 18:08
    which are all, like, these giant word processors that are focused on providing printed transcripts,
  • 18:08 - 18:11
    and have very rudimentary control over the OS.
  • 18:11 - 18:14
    Plover is designed to have complete control over the OS.
  • 18:14 - 18:17
    So you can use it for anything
    you can use your qwerty keyboard to do.
  • 18:17 - 18:23
    It still needs just-in-time
    dictionary entries to be really, really useful.
  • 18:23 - 18:26
    But other than that, it's pretty much working quite well.
  • 18:26 - 18:28
    A couple of little bugs.
  • 18:28 - 18:33
    But very few people -- as, you know, you asked me --
    who actually uses Plover?
  • 18:33 - 18:36
    Not that many people use Plover on a regular basis.
  • 18:36 - 18:41
    I use it for transcribing on the train, because I don't like carrying my big steno machine --
  • 18:41 - 18:43
    you know, taking it out on the train and transcribing stuff.
  • 18:43 - 18:46
    So I can just use this little keyboard, which is much easier.
  • 18:46 - 18:47
    So I use it occasionally.
  • 18:47 - 18:50
    It's also my backup machine in case this one breaks,
  • 18:50 - 18:52
    which it has.
  • 18:52 - 18:57
    And I know of a couple people who started out learning steno from Plover
  • 18:57 - 18:59
    and then eventually got hooked and wound up buying
  • 18:59 - 19:01
    proprietary software and proprietary hardware,
  • 19:01 - 19:05
    because they decided to become professional stenographers.
  • 19:05 - 19:06
    Which is cool.
  • 19:06 - 19:08
    I like being a gateway drug to professional stenography.
  • 19:08 - 19:13
    But I would much rather get people actually using Plover,
  • 19:13 - 19:15
    make it useful enough that they can actually use it,
  • 19:15 - 19:20
    rather than having to downgrade to these $4000 systems.
  • 19:20 - 19:22
    How did that happen?
  • 19:22 - 19:23
    Okay.
  • 19:23 - 19:26
    Hover Plover is my way that I think I can get people into it.
  • 19:26 - 19:28
    It's going to be a suite of little minigames.
  • 19:28 - 19:31
    How many of you guys have played typing games?
  • 19:31 - 19:33
    Yeah, exactly.
  • 19:33 - 19:34
    And they're fun, right?
  • 19:34 - 19:38
    They're actually even more fun with steno, because they're slightly more complex.
  • 19:38 - 19:40
    You're not just doing the little home row tippy-tappy.
  • 19:40 - 19:42
    You know, it's...
  • 19:42 - 19:45
    You have to bring in these dictionary entry incorporations,
  • 19:45 - 19:48
    defining your arbitrary mnemonic briefs.
  • 19:48 - 19:52
    And, you know, you're stroking out whole words.
  • 19:52 - 19:56
    So you can do something like a Guitar Hero-style thing,
  • 19:56 - 19:59
    but you're actually writing all of the lyrics
    to the songs you're listening to.
  • 19:59 - 20:01
    You know, in one stroke.
  • 20:01 - 20:01
    It's really fun.
  • 20:01 - 20:03
    It's actually a hypnotic kind of thing.
  • 20:03 - 20:06
    Once you get into the groove,
    and you're writing everything you hear,
  • 20:06 - 20:09
    and it's coming out through your fingers
    and onto the screen.
  • 20:09 - 20:10
    It's a very pleasant sensation.
  • 20:10 - 20:14
    So I've got a couple of ideas for the minigames
  • 20:14 - 20:19
    that we can use as part of the tutorial to teach people steno in the most painless way possible.
  • 20:19 - 20:21
    Because right now...
  • 20:21 - 20:22
    Oh, man.
  • 20:22 - 20:23
    I went to court reporting school.
  • 20:23 - 20:26
    Because there is no school to teach you how to provide realtime for the deaf.
  • 20:26 - 20:30
    There's only court reporting.
  • 20:30 - 20:34
    And then you have to sort of teach yourself
    the realtime side of the business.
  • 20:34 - 20:37
    And it's sitting in a room for three hours,
  • 20:37 - 20:41
    while someone reads you jury charges, basically.
  • 20:41 - 20:43
    Like, legal material, you know.
  • 20:43 - 20:45
    And they start out at 60 words a minute.
  • 20:45 - 20:47
    And then once you pass that test,
    you go to 80 words a minute.
  • 20:47 - 20:50
    And it's tedious and it's grueling.
  • 20:50 - 20:53
    And it costs, like, 300 bucks a month.
  • 20:53 - 20:56
    And there's an 85% dropout rate in steno schools.
  • 20:56 - 20:58
    It's kind of a scam.
  • 20:58 - 21:00
    They're all for-profit schools.
  • 21:00 - 21:02
    It's a bad scene.
  • 21:02 - 21:06
    I think getting people
    to actually use this while having a good time
  • 21:06 - 21:10
    and getting, like, competitive about showing up
    on the high score tables
  • 21:10 - 21:14
    is the way to really get a solid user base of steno users.
  • 21:14 - 21:17
    So I'm just going to give you a couple screenshots.
  • 21:17 - 21:18
    Like, mockups, obviously.
  • 21:18 - 21:20
    Hover Plover does not yet exist,
  • 21:20 - 21:25
    because, sadly, I'm kind of tapped out on funding for Plover.
  • 21:25 - 21:28
    I'm looking for alternate sources.
  • 21:28 - 21:31
    And Hover Plover hasn't really...
  • 21:31 - 21:36
    I commissioned a couple of screenshots to see what the minigames might look like,
  • 21:36 - 21:40
    but until I get some development money,
  • 21:40 - 21:43
    Hover Plover will not exist yet.
  • 21:43 - 21:48
    But here's what I'm hoping it'll look like when it does exist.
  • 21:48 - 21:51
    So that's the Plovercraft, right?
  • 21:51 - 21:54
    And your Plovercraft is busted.
  • 21:54 - 21:56
    It can only go up.
  • 21:56 - 21:58
    You know, and it can't navigate around obstacles.
  • 21:58 - 21:59
    So you're...
  • 21:59 - 22:01
    It's a 2D side-scrolling platformer.
  • 22:01 - 22:04
    So you have to navigate
    around all these obstacles by pressing the word,
  • 22:04 - 22:08
    by typing the word,
    so it'll like zoom you up above the obstacle.
  • 22:08 - 22:10
    And then you'll start dropping back down again,
  • 22:10 - 22:13
    to try to get to the repair shop to fix your Plovercraft.
  • 22:13 - 22:18
    So the word "compression" in steno is spelled K-P-R-E-G-S.
  • 22:18 - 22:23
    The GS is the "shun" ending and the KP is sort of "k'puh."
  • 22:23 - 22:25
    It's semi-phonetic.
  • 22:25 - 22:28
    There's lots of little shortcut tricks, you know?
  • 22:28 - 22:30
    So you type that, and your Plovercraft zooms up.
  • 22:30 - 22:33
    And, you know, you have to navigate around the stray cats
  • 22:33 - 22:35
    and water towers and whatever else.
  • 22:35 - 22:37
    I think it'll be awesome.
  • 22:37 - 22:41
    The other mini game that I've got an idea for...
  • 22:41 - 22:42
    (laughter)
  • 22:42 - 22:45
    Yeah, so this is a...
  • 22:45 - 22:48
    This is a top-down space shooter, basically.
  • 22:48 - 22:51
    So you've got your little simple one-stroke words,
  • 22:51 - 22:54
    like "snails" and "antidisestablishmentarianism."
  • 22:54 - 22:55
    Easy peasy, right?
  • 22:55 - 22:59
    Then you've got your slightly more challenging two-stroke words like "guardian".
  • 22:59 - 23:01
    Slightly more challenging.
  • 23:01 - 23:03
    "Bemusement"; three-stroke.
  • 23:03 - 23:05
    And then you got something like this.
  • 23:05 - 23:08
    This giant scary laser ship, which is an undefined.
  • 23:08 - 23:11
    So it's a word that doesn't appear in your dictionary.
  • 23:11 - 23:12
    And you gotta figure out quickly
  • 23:12 - 23:14
    what you want to define it as, define it,
  • 23:14 - 23:20
    and then it goes down to these little,
    you know, depending on how many strokes it is,
  • 23:20 - 23:21
    it'll go down to that stroke.
  • 23:21 - 23:23
    So "frangipani" -- probably a three-stroke word.
  • 23:23 - 23:24
    Not too scary.
  • 23:24 - 23:28
    As long as you can define it in time, you have no problem.
  • 23:28 - 23:29
    And you've gotten 107 defines already,
  • 23:29 - 23:33
    so you're gonna be fine.
  • 23:33 - 23:35
    That is basically...
  • 23:35 - 23:36
    Sorry, that cut off.
  • 23:36 - 23:38
    That's basically my talk.
  • 23:38 - 23:40
    I'm very happy to answer any questions
  • 23:40 - 23:41
    that you guys might have.
  • 23:41 - 23:45
    But if you're interested,
    or know someone else who might be interested,
  • 23:45 - 23:47
    I really --
  • 23:47 - 23:50
    I need some kind of a buttkick to get this going again.
  • 23:50 - 23:54
    It's been on hiatus for about six months,
    ever since I ran out of money,
  • 23:54 - 23:56
    and Josh had a baby and moved to the west coast.
  • 23:56 - 24:03
    So I'd love any ideas on raising capital.
  • 24:03 - 24:06
    Or if you know of anyone
    who might want to use the software.
  • 24:06 - 24:10
    Or if you guys are interested
    in using the software, please let me know.
  • 24:10 - 24:12
    Email me.
  • 24:12 - 24:13
    Comment on the blog.
  • 24:13 - 24:16
    I'll probably be posting these slides on the blog.
  • 24:16 - 24:21
    And the Google group is cut off down there,
    but it's linked on the blog.
  • 24:21 - 24:23
    So that's pretty much it.
  • 24:23 - 24:24
    Thank you.
  • 24:24 - 24:28
    (applause)
  • 24:28 - 24:31
    Any questions?
  • 24:31 - 24:34
    >> You just need funding for the game?
  • 24:34 - 24:37
    Yeah, and, like, a little more work on Plover.
  • 24:37 - 24:39
    Like, this one feature needs to be developed.
  • 24:39 - 24:43
    >> Have you thought about maybe getting in touch with one of the Python start-up groups,
  • 24:43 - 24:47
    or doing a workshop to introduce people to programming,
  • 24:47 - 24:50
    and getting them up to speed?
  • 24:50 - 24:52
    Because maybe they can take on
    one of the games as a project.
  • 24:52 - 24:57
    Well, at this point I'm still sort of trying to gauge demand,
    because I get a lot of different responses.
  • 24:57 - 25:00
    I mean, you guys obviously cared enough
    to come to the presentation.
  • 25:00 - 25:06
    How many of you think that learning Plover might be a fun and/or useful thing to do at some point?
  • 25:06 - 25:07
    So, like, most of you.
  • 25:07 - 25:09
    That's encouraging.
  • 25:09 - 25:11
    I know there's some selection bias,
    because you came to this talk.
  • 25:11 - 25:16
    But it also proves
    that I didn't totally turn you off the idea, and so...
  • 25:16 - 25:17
    Yeah?
  • 25:17 - 25:20
    >> So I was curious why it was Linux-only,
  • 25:20 - 25:21
    and you say it's a keyboard emulator, but I'm wondering --
  • 25:21 - 25:23
    what is the code base written in?
  • 25:23 - 25:28
    Could it be Python libraries or some sort of HTML5,
    so you could use it anywhere?
  • 25:28 - 25:29
    And could it go on GitHub?
  • 25:29 - 25:33
    Okay, we started on GitHub and then moved to Launchpad.
  • 25:33 - 25:40
    But the reason why it's currently Linux-only is because
    the code for the keyboard emulation
  • 25:40 - 25:43
    is taken from xkey, which I think was written in Python.
  • 25:43 - 25:48
    So it was pretty easy to incorporate it
    into the rest of Plover's Python code.
  • 25:48 - 25:53
    The equivalent to xkey in Windows is AutoHotKey,
    which is written in C.
  • 25:53 - 25:57
    So I think it will be a more complex job to sort of mash those two together and make them work.
  • 25:57 - 25:59
    So that's basically it.
  • 25:59 - 26:02
    I would definitely like to port to Windows,
    because I think that would open it up a lot.
  • 26:02 - 26:06
    But it's going to take a little more
    development effort to do that.
  • 26:08 - 26:09
    Yeah?
  • 26:09 - 26:16
    >> Do you think there's a lot of demand at most any university to have someone caption lectures?
  • 26:16 - 26:18
    Well, there certainly is in New York City.
  • 26:18 - 26:23
    Like I said, I've had to turn down
    five or six students this semester,
  • 26:23 - 26:26
    which is terrible, because it means that these people
    are basically not getting a education.
  • 26:26 - 26:29
    Dental school, medical school...
  • 26:29 - 26:33
    These are people who have worked their entire lives
    to get where they are,
  • 26:33 - 26:35
    and now they're trying to go to school
    without any accommodations,
  • 26:35 - 26:38
    because the people just aren't on the ground.
  • 26:38 - 26:41
    It's a terrible state of affairs.
  • 26:41 - 26:44
    So not all universities are willing to pay for accommodations,
  • 26:44 - 26:51
    because, you know, it is a difficult skill to learn,
    and it's expensive to hire someone like me.
  • 26:51 - 26:54
    But some schools definitely are, so there's a huge demand.
  • 26:54 - 26:55
    Yeah?
  • 26:55 - 27:00
    >>> My wife goes to dental school, and there's one student who listens to lectures,
  • 27:00 - 27:02
    as well as type at the same time.
  • 27:02 - 27:06
    Creates a transcript, and he obviously sells on the portal.
  • 27:06 - 27:07
    Yeah.
  • 27:07 - 27:09
    But he just types, like, qwerty-style?
  • 27:09 - 27:11
    >> Um, I'm not sure how he...
  • 27:11 - 27:13
    But yes, those transcripts are available.
  • 27:13 - 27:20
    So the question from my wife was: How can he pay attention to the class, as well as type it?
  • 27:20 - 27:27
    He just types, and when he goes home, he reads,
    and if he has a question, he goes to the professor.
  • 27:27 - 27:34
    The good thing is: Many students, they don't attend the lecture, or partial lecture, it's kind of helpful to read.
  • 27:34 - 27:39
    They have recordings,
    but not all professors have recordings.
  • 27:39 - 27:46
    If they want to get a recording, they need to have a TA,
    and they need to pay the TA, and it's kind of expensive.
  • 27:46 - 27:50
    And also searchable text is much more useful for studying purposes than a long, linear sound file.
  • 27:50 - 27:55
    But -- so, first of all, to address that,
    he's probably not getting everything verbatim,
  • 27:55 - 27:57
    obviously, if he's just doing qwerty.
  • 27:57 - 27:59
    Although some typists are pretty good.
  • 27:59 - 28:02
    They can get about half of the salient details.
  • 28:02 - 28:06
    Second of all, I learn a hell of a lot when I'm transcribing.
  • 28:06 - 28:10
    You know, it goes in through my ears and out through my fingers, but it leaves something behind.
  • 28:10 - 28:13
    So, I think it's actually a pretty good...
  • 28:13 - 28:18
    I know of at least one person
    who taught himself steno while going to school.
  • 28:18 - 28:20
    Like, pre-pharmacy school.
  • 28:20 - 28:21
    And got really good grades.
  • 28:21 - 28:24
    But then decided he would rather
    be a stenographer than a pharmacist.
  • 28:24 - 28:27
    So now he's getting into doing what I do,
  • 28:27 - 28:29
    and working for Deaf and hard of hearing college students.
  • 28:29 - 28:34
    >> Is there a clearinghouse site anywhere
    for captioning and steno jobs?
  • 28:34 - 28:37
    No, it's mostly independent contractors.
  • 28:37 - 28:39
    It's a very fractured field.
  • 28:39 - 28:46
    >> So basically, if you were looking for work,
    there isn't a place you would go, other than to agencies?
  • 28:46 - 28:51
    I just send my resume out to all 26 universities
    in the New York City area,
  • 28:51 - 28:53
    and they come to me.
  • 28:53 - 28:54
    Did you have a question?
  • 28:54 - 28:55
    >> About the library, so...
  • 28:55 - 28:57
    Is she using steno right now?
  • 28:57 - 28:59
    Yeah, she's using proprietary software.
  • 28:59 - 29:03
    >> But you were saying you had to declare some variables.
  • 29:03 - 29:09
    And that stenographers have their own library,
    and stuff like that -- how does that part tie in?
  • 29:09 - 29:13
    So you just tell it -- this is how I would spell compression,
  • 29:13 - 29:15
    and there's a way you can add this stuff
  • 29:15 - 29:16
    while you're doing it?
  • 29:16 - 29:19
    Yeah, well, this is the one feature that Plover is currently missing that it really needs to have
  • 29:19 - 29:21
    in order to be very useful.
  • 29:21 - 29:23
    I was assuming in that Zork thing --
  • 29:23 - 29:27
    that it had already been implemented, yeah.
  • 29:27 - 29:30
    >> So the feature that Plover needs
    is the ability to add in your own new entries?
  • 29:30 - 29:32
    Exactly; from the writer.
  • 29:32 - 29:33
    I mean, you can do it --
  • 29:33 - 29:36
    you can edit the text file manually, you know.
  • 29:36 - 29:39
    But being able to do it without breaking
    the stream of text is very useful,
  • 29:39 - 29:41
    and I do all the time in my proprietary software.
  • 29:41 - 29:43
    >> So you just shift into a mode?
  • 29:43 - 29:45
    Uh-huh, yeah.
  • 29:48 - 29:54
    >> So how long would it take for the average beginner
    to reach 200 words per minute with steno?
  • 29:54 - 29:56
    200 is tricky.
  • 29:56 - 30:05
    I find most people get up to around
    100 or 120 within four to six months,
  • 30:05 - 30:09
    and then they usually hit a wall and then plateau for a while.
  • 30:09 - 30:13
    And so once you hit your first big plateau,
    it's tough to get above that.
  • 30:13 - 30:17
    I got from 0 to 225 in a year and a half.
  • 30:17 - 30:22
    And that was me probably in front of the machine
    about 60 hours a week,
  • 30:22 - 30:26
    because I was doing it at my day job,
    and I was also practicing on my own time.
  • 30:26 - 30:33
    But most people can probably get up to 120-140
    within, you know, three to six months.
  • 30:33 - 30:35
    And if Hover Plover is addictive enough,
  • 30:35 - 30:40
    addictive enough that it gets people,
    you know, spending all night doing this --
  • 30:40 - 30:41
    which it really can.
  • 30:41 - 30:44
    I know people who do just regular steno for hours,
  • 30:44 - 30:48
    and they get sucked into this steno hole,
    and it's really engrossing.
  • 30:48 - 30:52
    You know, if it's addictive enough
    and people are spending a lot of time on it,
  • 30:52 - 30:55
    their rates will go up really quickly.
  • 30:57 - 30:58
    Yeah?
  • 30:58 - 31:01
    >> Can you give me the details
    on adding a word on the fly like that?
  • 31:01 - 31:04
    I'll tell you how my proprietary software does it.
  • 31:04 - 31:10
    I invoke a macro on my steno machine,
    which is GLBL, short for "global this word."
  • 31:10 - 31:15
    It pops up a window, which is, like, big
    and in the middle of the screen and obnoxious,
  • 31:15 - 31:17
    unless I make it invisible.
  • 31:17 - 31:21
    Plover will have a simple, discrete
    one-line window in the taskbar.
  • 31:21 - 31:25
    But my proprietary software --
    it's a huge, giant, unsightly thing.
  • 31:25 - 31:29
    Anyway, I press GLBL, a window pops up,
  • 31:29 - 31:34
    and it gives me the opportunity to tap out
    the word that I want letter by letter in English,
  • 31:34 - 31:39
    and then to enter the steno strokes that correspond to it.
  • 31:39 - 31:41
    So it just maps that, puts it in the dictionary,
  • 31:41 - 31:44
    and then every time you enter the steno strokes,
    it comes out with the English.
  • 31:44 - 31:49
    >> So this window pops up, you do that,
    you're done with that, you close the window,
  • 31:49 - 31:53
    and it injects that new word into your stream,
    and you're back to going along --
  • 31:53 - 31:55
    Exactly.
  • 31:55 - 31:59
    >> And so I'm thinking about keyboard shortcuts
    and how often there's conflicts.
  • 31:59 - 32:07
    So, in steno, how well are you able to go,
    "Well, this is the new keystroke,"
  • 32:07 - 32:10
    and not have it hit, like, a bazillion possibilities?
  • 32:10 - 32:11
    That's a really good point, actually.
  • 32:11 - 32:13
    Thank you for bringing that up,
    because I hadn't mentioned it.
  • 32:13 - 32:15
    I'm a Vim user.
  • 32:15 - 32:19
    You know, and so you've got, in Vim,
    every key mapped to a command.
  • 32:19 - 32:21
    A bit of a learning curve.
  • 32:21 - 32:23
    But once you learn it, it's very useful.
  • 32:23 - 32:27
    And there's some, you know,
    slight mnemonic things involved.
  • 32:27 - 32:29
    Like B takes you back.
  • 32:29 - 32:30
    F finds stuff.
  • 32:30 - 32:31
    Whatever.
  • 32:31 - 32:33
    Steno, first of all, is much more mnemonic,
  • 32:33 - 32:36
    because it's tied to syllables, rather than to initial letters.
  • 32:36 - 32:41
    So you're able to remember many more
    different commands.
  • 32:41 - 32:44
    And the question of conflicts --
  • 32:44 - 32:48
    they're usually pretty easy to avoid
    if you make them sound like an English word,
  • 32:48 - 32:50
    but they're not actually an English word.
  • 32:50 - 32:54
    You know, so my brief for "ridiculous" is "RILGS."
  • 32:54 - 32:57
    You know, to the point where I sometimes say it in English.
  • 32:57 - 32:59
    Like, "Dude, that's totally rilgs."
  • 32:59 - 33:01
    (laughter)
  • 33:01 - 33:04
    Or, like, the brief for "necessarily" is "NELS."
  • 33:04 - 33:06
    You know, it's pronounceable.
  • 33:06 - 33:07
    It's very memorable.
  • 33:07 - 33:12
    But it doesn't conflict with anything in English,
    because it's not a valid English syllable.
  • 33:12 - 33:18
    So for command strokes, it's, you know,
    pretty simple to come up with something
  • 33:18 - 33:21
    that's very easy to remember, very easy to write, but has...
  • 33:21 - 33:25
    You have many, many more options.
  • 33:25 - 33:30
    You know, with Vim, you just have basically the qwerty keyboard; that's 112 possible commands.
  • 33:30 - 33:36
    For steno, you can have innumerable commands,
    because they're tied to syllables rather than to letters.
  • 33:36 - 33:40
    >> Do you have punctuation on your keyboard,
    like curly braces and things like that?
  • 33:40 - 33:41
    Oh, yeah, totally.
  • 33:41 - 33:45
    I don't know if any of you guys
    saw me caption any of the talks.
  • 33:45 - 33:47
    I didn't put any underscores when they appeared,
  • 33:47 - 33:53
    because even though I told my proprietary
    steno software to define "RUND" as underscore,
  • 33:53 - 33:57
    it decided it didn't want to do that.
  • 33:57 - 33:58
    So it just didn't just happen.
  • 33:58 - 34:00
    Sorry about that.
  • 34:00 - 34:02
    My software, $4,000 software.
  • 34:02 - 34:03
    >> Didn't work, huh?
  • 34:03 - 34:06
    Are you kidding me?
  • 34:06 - 34:09
    They don't even have Word Wrap on this thing.
  • 34:09 - 34:14
    Seriously, we had to set the margins, like,
    really kind of bigger than we wanted to,
  • 34:14 - 34:17
    because otherwise it would just start scrolling off the screen.
  • 34:17 - 34:19
    It's pathetic.
  • 34:19 - 34:23
    And I have to pay $700 a year just to get the upgrades.
  • 34:23 - 34:27
    >> Are you actually using Plover at all, or is it still --
  • 34:27 - 34:32
    Yeah, as I said, I have it as a backup
    in case my proprietary stuff goes down.
  • 34:32 - 34:37
    And I do occasionally use it when doing
    offline transcription for medical journals,
  • 34:37 - 34:42
    because it's easier to take out the qwerty keyboard
    than to take this thing out.
  • 34:42 - 34:43
    Um, yeah?
  • 34:43 - 34:46
    >> Can you remap your qwerty keyboard into chords?
  • 34:46 - 34:48
    You don't have to remap it.
  • 34:48 - 34:53
    When Plover's turned on, it just sends out steno,
  • 34:53 - 34:55
    and when you turn it off, it just goes back to qwerty.
  • 34:55 - 34:58
    The only modification I made was
    I put a couple of leather keypads
  • 34:58 - 35:02
    on the keys used for steno, just for some haptic feedback.
  • 35:04 - 35:06
    It's very simple.
  • 35:06 - 35:08
    If anyone wants to come up and try it out...
  • 35:08 - 35:10
    Well, I think I probably have to go
    to the next lecture to caption.
  • 35:10 - 35:13
    But thank you so much for coming.
  • 35:13 - 35:16
    And if you have any questions,
    please contact me, and I'd love to talk to y'all.
  • 35:16 - 35:17
    Bye.
Title:
Video Language:
English

English subtitles

Revisions