Saturday, March 30, 2013

PyCon Video

Here's the captioned video of my PyCon talk.

Here's the page with the slides and the uncaptioned YouTube version of the video. Hopefully when I give the caption file to the people in charge of the videos, they'll upload it to the YouTube version so that'll have captioning too.

Saturday, March 16, 2013

Status of Current Tasks Page is Back

In preparation for my talk tomorrow, I've resurrected the Status of Current Tasks page on the Plover Wiki, which was pulled when the wiki went down a few months ago and which had fallen disgracefully out of date. It contains some of the top priority bugs and issues from the Github, plus ideas to improve and expand the Plover community in the categories of hardware, steno pedagogy, and general promotion of all things open source and stenographic. Go check it out, and if anything appeals to you, contribute!

Friday, March 8, 2013

Using Plover for Python

I gave a dry run of my PyCon presentation at the New York Python Meetup last night, and I think it went quite well! I think I've finalized my slide deck. Longtime followers will notice that I reused a few slides from my 2011 PyGotham presentation, but I've added and changed a fair amount of stuff. I think it's tighter and flows more smoothly than the old version. Anyway, as part of the presentation, I made a very quick video showing me using Plover to write a small snippet of code from my Codecademy Python Course. I also added a closed captioning track showing the pseudosteno for every stroke I was writing. It doesn't show me making new definitions or anything like that, since that feature is still being implemented (it's a little too buggy for release at the moment), but I think it gets across how easy it is to write quick, smooth, efficient Python code using steno. For some reason, when I tell people about steno, they often don't understand how a keyboard consisting of 22 letters can be used to write punctuation, meta keys, and commands, so I think this video is useful to demonstrate that it's as simple as defining PRENS as (), TA*B as the Tab command, RIPT as raw_input(", et cetera, and then just barreling on through your code without a second thought.