I have been dreading writing the chapter about QWERTY and Dvorak for months. But now that it’s next on the docket, I find myself really excited to tackle it. Perhaps going through other tough chapters emboldened me, or perhaps there’s a huge element of randomness to all this.
-
-
Replying to @mwichary
it me (An illustration for an article about the future of books. Popular Computing, November 1985. Illustrator: Kent Smith.)pic.twitter.com/tKgbNEln7h
2 replies 1 retweet 21 likes -
Replying to @mwichary
Partly eager to finish the first draft just so I could run some statistical analysis on what I wrote.
1 reply 0 retweets 4 likes -
Replying to @mwichary
Having conversations with myself a year ago (or, celebrating how much I learned in the interim).pic.twitter.com/izfltEYrFR
1 reply 0 retweets 3 likes -
Replying to @mwichary
Okay, tomorrow’s The Big One. The trickiest of all chapters: All the myths and truths of QWERTY and Dvorak. I spent so much time researching this. The notes alone are 14,000 words. Here’s the lists of all my to-dos, and an already serious batch of title contenders. Let’s go.pic.twitter.com/DwP8fIOoZT
5 replies 0 retweets 17 likes -
Replying to @mwichary
Wow. I was a big Dvorak fan for a while. I once remapped my keyboard and learned to type 10 wpm. But this was in Emacs, and I had only remapped the chars being inserted, not the control chars. I gave up at that point since I didn't want to relearn all the control chars.
1 reply 0 retweets 1 like -
Replying to @stuartmarks
Yeah, Dvorak on Mac OS has a mode where holding Command doesn’t remap QWERTY – only regular typing.
1 reply 0 retweets 0 likes -
-
-
Replying to @mwichary
I'd love to hear your experiences. From what I recall, I could feel my fingers moving less, since the most common letters were on the home row. But it was still frustratingly slow compared to qwerty, where I could (and still can) type > 100 wpm.
1 reply 0 retweets 0 likes
Yeah, I can do around 110 wpm myself on QWERTY, so I’m definitely not doing that while writing the book. :·]
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.