Showing posts with label Dvorak. Show all posts
Showing posts with label Dvorak. Show all posts

Thursday, January 31, 2019

From the Archives - Typing Tutor Corporate Intrigue!


Introduction

Sometimes technical support really lets me down. And then, when I want to gripe about it, who wants to listen? This post, from my archives, recalls an email exchange with tech support that bled over into my personal life, when I forwarded the thread, with my commentary, to my brothers and my dad. I somehow really ruffled my dad’s feathers, and his peeved response to my email provoked a whole new level of my scorn.

(The original version of this post didn’t disclose that it was my dad I was responding to. I called him “P—” because he probably wouldn’t like being quoted here, and I couldn’t just get his permission because he was dead. I took some solace in knowing that his being dead would somewhat mitigate the consequences of anybody figuring out who he is. Er, was. But it’s been a few years now, and honestly I think my original discretion was perhaps unnecessary. Don’t worry, he won’t be rolling in his grave because he was cremated.)



Typing Tutor Corporate Intrigue – April, 2002

From: Albert, Dana P.
Sent: Monday, April 22, 2002 4:28 PM
To: support@ssi.com
Subject: Question about Typing Tutor

Hi,

I just bought Typing Tutor 9. I see from your website that version 12 is available, but I can’t find it for sale anywhere. I’m hoping v9 is good enough.

My question concerns your Conceptual Effects Typing Method (CETM) training scheme and the Dvorak keyboard layout. I bought your product, over competing ones, because I wanted to try the CETM method, and I’m learning the Dvorak layout, and your software purports to support both. The problem is, the Dvorak layout seems only to be supported by your standard tutorial mode, not the CETM mode. In other words, your software introduces the keys sequentially according to the QWERTY home row, even when I’m using the Dvorak configuration. Is there a way around this, perhaps a patch I could apply to the program? Do more recent versions of the software support this?

Thanks,
Dana

--~--~--~--~--~--~--~--
From: support@ssi.com
Sent: Wednesday, April 24, 2002 2:46 PM
To: ‘Albert, Dana P.’
Subject: RE: Question about Typing Tutor

Actually, the latest edition does not support the Dvorak keyboard at all. Support for it has declined with the rise in carpel tunnel injuries from over use of the keyboard.

M— B—
S.S. Interactive


--~--~--~--~--~--~--~--
From: Albert, Dana P.
Sent: Wednesday, April 24, 2002 5:16 PM
To: ‘support@ssi.—.com’
Subject: RE: Question about Typing Tutor

M—,

Are you saying that use of the Dvorak keyboard has been associated with carpal tunnel injuries? This seems counter-intuitive based on the purpose of the Dvorak layout. Is there any documentation to this effect? If there are risks associated with this layout I want to know about them!

Thanks,
Dana

--~--~--~--~--~--~--~--
From: support@ssi.com
Sent: Monday, April 29, 2002 3:19 PM
To: ‘Albert, Dana P.’
Subject: RE: Question about Typing Tutor

No formal scientific studies have been done. Some say that it relieves symptoms but on the other hand, if the speed increases dramatically, you are back in the repetative [sic] motion issue.

M— B—
S.S. Interactive


--~--~--~--~--~--~--~--
From: Albert, Dana P.
Sent: Monday, April 29, 2002 4:34 PM
To: Geoff Albert; Bryan Albert; Dad
Subject: FW: Question about Typing Tutor

Dudez,

Remember that Typing Tutor problem I was talking about, where the lessons weren’t tailored to the Dvorak keyboard as promised? I emailed tech support, and they basically blew me off. I’m not going to pursue the matter with the hapless support rep, M— B—, because to challenge her out-of-thin-air BS explanations, employing my relentless rhetorical style, would be cruel. But check out her emails (attached). Unbelievable. Just to blow off a little steam I’ll share my objections with you.

If no study has been done, on what basis did they drop Dvorak support? And I have to take issue with the idea that increased comfort doesn’t relieve repetitive stress disorder because the increased speed results in more typing. This is only true if there is an infinite amount of typing to do. But if I’m faster, isn’t it the case that I finish earlier and can spend more time at the water cooler resting my hands? (Never mind that my employer took away our water coolers, in addition to our coffeemakers, and are putting in a vending machine. Those are mere technicalities.)

The more I think about it, the more M—’s logic befuddles me. If speed is bad, because it increases the likelihood of repetitive stress disorder, why is SS Interactive producing software that helps you increase typing speed? If they really care about repetitive stress disorder, why not either get out of the business entirely, or teach a more ergonomic typing technique (e.g., Dvorak)? And while I’m at it, wouldn’t “repetitive stress disorder” be a great name for a rock band? (“Coming to the Palladium: Repetitive Stress Disorder, with special guest Hard Floor Tool!”)

Dana

--~--~--~--~--~--~--~--
From: Dad
Sent: Monday, April 29, 2002 9:56 PM
To: Albert, Dana P.
Cc: Geoff; Bryan
Subject: fellows: Re: FW: Question about Typing Tutor

Dana,

The lady you are dealing with is merely covering for her managers. They have almost certainly decided, as one learns to do in management school, to eliminate any products whose monetary return is not dramatic. Ms B— might quickly lose her job if she backed down on the validity of the things she has said. Surely her email transactions are monitored sometimes or all the time. It is not worth costing her her livelihood to prove that you are right. It’s the managers who should be punished, but you have no safe means to do that, and it would not get you the desired software. Why continue?

Dad

--~--~--~--~--~--~--~--
From: Albert, Dana P.
Sent: Tuesday, April 30, 2002 5:03 PM
To: Bryan; Geoff
Subject: FW: fellows: Re: FW: Question about Typing Tutor

[Dad omitted from this response]

Dudez,

“Why continue?” Why indeed! Naturally I will not rest until I have entrapped Ms B—, pawn that she is, in my remorseless game of corporate intrigue. Yes, I have set a trap—my e-mail messages are the bait, and she is my prey. I’m sure her evil employers have a zero-tolerance policy concerning failure to further the corporation’s diabolical deceptions. It is intuitively obvious that entire rooms full of lowly auditors pore over e-mail after e-mail looking for signs of dissent. Sure, I’d like to punish those managers, ensconced in their comfortable boardrooms, plotting their schemes to catch disloyal tech support people in the act of being bullied, by the likes of me, into betraying the evil business school secrets. But if I can’t catch the big fish, I’ll settle for ending the humble career of a mere clerk. Such is my insatiable lust for winning arguments, even if I’m arguing with unlearned, weary cogs of corporate America. If I can have the satisfaction of taking food right out of the mouths of Ms B—’s children, that’s enough for me. Here is my fantasy, which I run through in my head, night after night, in salacious detail: 

         Ms B— reads my retort, which lays bare the flaws in her statements about Dvorak and Typing Tutor 9. Realizing she is outsmarted, and can no longer continue her deception, she replies, “You’re right! I can’t deny it! It has nothing to do with carpal tunnel! It’s you—you’re not a preferred customer! You had it right all along! Please, please forget about Typing Tutor, forget this whole correspondence!” She clicks “Send” and then madly begins deleting the e-mail chain, message by message, from her PC, her face bright red. A colleague, a mere two feet away in a three-foot-wide cubicle identical to hers, sees her distress, guesses it’s corporate sabotage, and sends a quick message to her manager. In less than an hour the auditors have put together the incriminating trail of digital evidence, and Ms B— has been summoned and is standing in front of her boss, knees shaking.
         “Ms B—, was I not perfectly clear, in our staff meeting last October, what tech support personnel were to tell customers about our stance on Dvorak?”
         “You were,” she sobs.
         “This company cannot afford to support Dvorak users, and yet we cannot risk being sued for choosing not to support them. That is why you were to use carpal tunnel syndrome as an excuse for our product direction. Why have you betrayed our secret to a customer? Don’t try to deny doing it, I have the e-mail right here.”
         “I don’t know . . . I guess he bullied me into admitting it!”
         “Yes, it seems a very clever troublemaker with a big chip on his shoulder has it in for you. But damn it, you didn’t need to cave. I have your employment agreement right here. You have acknowledged, by your signature, that failure to align all of your customer-facing statements with our official corporate positions is grounds for immediate termination. Give me one good reason not to fire you.”
         “I’m the sole breadwinner for my family! My husband was arrested by the FBI for forwarding an article about PGP to a friend, so I’m raising the children all by myself!”
         “I’m afraid that’s not SSI’s problem. You have five minutes to clear out your desk. A security guard will escort you from the building. You’ll never work tech support again in this state, I can guarantee you that.” As the door closes behind her, she hears the beginning of a long peal of evil laughter.


Since when is Dad an expert on what “they” teach in “management school”? And where did he get his information about how closely companies monitor e-mail? Did this guy grow up in the Soviet Union or something?

And what’s this about “It’s the managers who should be punished, but you have no safe means to do that.” What does that even mean? Since when do managers get punished? And how would one do that safely?

Above all, how did Dad not grasp that my retort was hypothetical, and that I never intended to “continue”?

Sheesh,
Dana

--~--~--~--~--~--~--~---~--
For a complete index of albertnet posts, click here.

Monday, January 18, 2016

AI Smackdown - Moto vs. Cortana vs. Siri


NOTE:  This post is rated R for mild strong language.

Introduction

I already blogged about my Android phone—not the way a professional critic would, but in terms of what’s actually interesting about it, which to me is the Artificial Intelligence angle.  Actually, “artificial stupidity” was the point:  a phone playing dumb so it can play favorites.  I’ve also blogged a bit about AI in general, with Apple’s Siri agent as a case study, but that was before I had an iOS device.  Now, I own all three platforms:  Moto/Android; Siri; and Microsoft’s Cortana.  In this post I compare and contrast them: not because I’m going to help you choose, but to try to make you laugh.  And you might have something interesting to scratch your head about later.

(I’m not going to try to differentiate between the terms Google Now, Android, and Moto.  They all meld in my mind.  If somebody protests that there are massive differences, I won’t be offended if you go read his or her blog instead.)


Cortana

I’ll start with Cortana because it can be dispatched very quickly.  If you type something into the Cortana field in Windows 10, it does a Bing search.  Bing is a little bit like using a Curad bandage instead of a Band-Aid, or using Hunts ketchup instead of Heinz, or wearing Sears Toughskins jeans instead of Levi’s.  It just isn’t done.  I don’t actually care if Bing works just fine.  It’s Bing, which means it’s not Google. “Let me Bing that for you.”  Give me a break.

Moreover, before you can get into the voice recognition stuff, you have to deal with this frightening disclaimer:


Yes, I know all this meddlesome snooping is just to “tailor the experience,” but it’s the online equivalent of your tailor saying, “To get the fit right on these trousers, I’ll have to reach in and fondle your balls.”  The explicit information Windows wants to use is bad enough, but that wide-open phrase “and other information” is just over the top.

Besides, “Cortana” sounds like a new model of Hyundai.  You know what Microsoft?  It’s over.  You lost.  You’re just a PC software company.  Stop trying to act “mobile.”

Android/Moto

I won’t go into a lot of detail about how well my Android phone responds to voice commands, because a) I already did that, here; and b) as I describe the Siri experience, I’ll compare it to Android/Moto as I go.

The really lame thing about Siri

Imagine if, before engaging with a person, you had to go push a button on the person’s chest.  In most cases, this would be absurd.  (With my kids, who never hear my commands, it would actually be an improvement.)

I think it almost goes without saying that voice response is a minimum requirement for any kind of AI.  The Siri demo I watched way back in 2012 did feature voice activation on the iPhone.  But oddly enough, for the Siri voice response to work on the iPad, the iPad has to be plugged in to an electrical outlet.  That is just so bizarre!  I mean, the iPad’s portability is the whole point, isn’t it?  What’s next for Apple:  an iPhone you plug into an RJ-11 jack?  This is ridiculous.  If I’m sitting at a desk next to an electrical outlet, I might as well be using a laptop.

There’s something else really lame about the iPad:  a limitation that hasn’t existed on an Apple product since the Apple II computer.  But I’ll get into that later.  Better to keep you in suspense.

Siri voice response:  up to snuff?

In general, Siri tries to have a bit more personality than Moto.  For example, if I ask my Droid, “Do you love me?” it shows me a song called “Do you love me?” by the Contours.  (My younger daughter, who has not seen “Her,” put me up to asking this question.)  When I asked Siri if she loved me, she responded, “I respect you.”  And when (again at my daughter’s behest) I asked Siri, “Have you ever gone to the bathroom?” she replied, “Who, me?”

Is this cheekiness a good thing?  Well, Siri’s responses may strike you as funnier that Moto’s.  On the other hand, when I asked my Droid about using the bathroom, I got a list of hits pertaining to using the wrong restroom (i.e., the one intended for the opposite sex).  It was a very funny list, linking to some amusing sites.  (You may be wondering:  have I ever used the wrong restroom?  Well, yes, once, purely by accident.  I was in there doing my business and thinking, “What kind of public restroom doesn’t have urinals?”  When the answer suddenly came to me, I hightailed it right on out of there.)

Sometimes Siri’s personality gets in the way.  For example, I asked Siri, “What time is it?” and she responded, “At the third stroke, it will be 16:26.  Beep.  Beep. Beep.”  This was more confusing than amusing, and besides, it was inaccurate:  the actual time was like 4:25:30.  I would rather Siri have a more reliable connection to the NIST Internet time servers than a zingy response.

If your desk is as cluttered as mine, being able to summon your phone by voice is very handy.  When I call out my keyphrase for my Droid, it makes a pretty loud two-tone beep to let me know it’s listening.  The iPad beep is much quieter.  Neither device responds in any useful way to the question, “Where are you?”  Siri says, “Wherever you are, that’s where I am.”  This isn’t that funny, and for most people wouldn’t even be true.  (I bring my iPad, Droid, silverware, and all other valuables with me wherever I go, so don’t bother burglarizing my house.)

 This is where these devices are inconsistent.  Their programmers need to decide if the device should have a sense of self or not.  Siri speaks in the first person (e.g., “Who, me?” and “I respect you”), but when I say, “Hey Siri, how’s your battery doing?” she has no idea what “your” means.  She replies, “My apologies ... I couldn’t find those stocks.”  Pretty useless.

When I tell my Droid, “Find my phone,” it makes this cool sonar sound continuously until I find and silence it.  When I tell Siri “Find my iPad,” she tries to make me turn on Location Services.  Look, Siri, if I could do that, I’d know where you are, and I wouldn’t be asking.

I’ve often thought that one of the most useful features of voice response would be getting help configuring the device.  So I said, “Hey Siri, turn on your flash.”  She replied,  “Who, me?”  I decided some context might help, so within the camera app I said to turn on the flash.  Siri replied, “It doesn’t look like you have an app named ‘flash.’  If you’d like, I can help you look for it on the App Store.”  I just don’t think this is that difficult a concept.  You have a camera.  It has a flash.  Turn it on.

The Droid does respond to “Take a selfie.”  It ought to say, “I can’t,” because its camera is basically its face.  But its reaction, which is to launch the camera, put it in selfie mode, and set a self-timer, is actually fairly useful, at least for the hands-free breed of narcissist.  When I tell Siri “take a selfie,” she says, “You’ll need to unlock your iPad first.”  This isn’t very helpful, and in fact isn’t even true.  As my older daughter discovered, the iPad can be used as a camera even by somebody who lacks my fingerprint and passcode.  And when I follow Siri’s instructions and unlock the iPad, it does go into camera mode, but not selfie mode.  As regards this command, Siri is fairly incompetent.

Something that bothers me about my Droid’s AI is a certain lack of resourcefulness.  When I ask it, “How do I look?” I think it should activate the camera in selfie mode, to use as a mirror.  Or It could really wow me by saying, “Your hair is a mess.”  (When you consider modern digital camera technology, which can tell if a subject’s eyes are closed, this hairdo check actually seems quite doable.) 

I asked Siri, “How do I look?” and she really stumbled.  She kept hearing, “How do I luck,” which she should have automatically revised because it just doesn’t make any sense.  One time, she thought I asked, “How do I lurk?” and replied, “I found something on the web about ‘how do I lurk.’ Check it out.”  That’s really unfortunate.  I wonder what kind of banner ads and spam I’ll get now that the Internet thinks I’m a stalker.

Finally Siri heard me right and replied, “Judging by your voice, I’d say you must be fairly attractive.”  Clever, but also kind of patronizing.  I mean, it’s bad enough asking an inanimate object such a personal question, but to be damned with faint praise ... that’s pretty pathetic.  I think Siri should be generous and say, “I would so go to bed with you.”

At least Siri respects my privacy.  When I said, “Get me home,” she replied, “I don’t know your home address.  In fact, I don’t know anything about you.”  I found this really reassuring, especially after Cortana’s attempted shakedown earlier.  (Yes, Siri did ask me to go into settings and identify myself, but didn’t require it.)

I have to say, though, there’s something a bit creepy about Siri.  When I ask something complicated, such as a question regarding navigation, there’s this little blurry light that bounces back and forth along the bottom edge of the screen, which reminded me of something sinister.  After racking my brain for awhile I realized what:  the single roving eye of a Cylon from “Battlestar Galactica.”  Is Siri some kind of kindred spirit to the AI powering the Cylons?  If so, that doesn’t reflect well ... the Cylons were really pretty stupid.  They always went down like bowling pins.

Another creepy thing:  when I said, “Hey Siri, lock my iPad,” she replied, “I’d like to, but I cannot.  My apologies.”  This almost gave me chills.  It brought me right back to the HAL 9000 in “2001 – A Space Odyssey,” when Dave says, “Open the pod bay doors, HAL,” and HAL replies, “I’m sorry, Dave.  I’m afraid I can’t do that.”  Who is Siri’s master:  me, or Apple?

Feature parity with Moto?

If I were designing Siri, or working on an update package, I’d pay close attention to what the competition is doing.  I’d make sure, for example, that anything Moto could do, Siri could do better.  This evidently hasn’t occurred to Apple, because there are all kinds of commands Moto can handle that Siri cannot.  For example, if you ask Moto, “What’s up?” it will trawl through your appointments, e-mails, etc. and give you an update.  I asked Siri “What’s up?” and she said, “I’m thinking about pie.  Mmmmmm.” 

If you tell Moto, “Talk to me,” it will announce incoming calls and texts for the next 30 minutes.  This doesn’t occur to Siri, who responds, “I’d really prefer it if you talked to me.  Tell me your hopes, your dreams, where you’d like to make a dinner reservation.”  So I told Siri, “I hope my dinner is yummy tonight.”  She replied, “I don’t know what you mean by ‘I hope my dinner is yummy tonight.’  How about a web search for it?”  Not a very good listener, since she specifically asked me to tell her my hopes!  Just lip service.  I said, “I dream of being rich and famous one day,” and got the same “I don’t know what you mean” response.

I said, “Hey Siri, play Beethoven on YouTube.”  She replied, “You don’t seem to have an app named ‘YouTube.’ We could see if the App Store has it.”  Don’t play dumb with me, Siri!

I asked Siri to zap my screen (which is how Moto is told to take a screen snapshot).  Siri kept hearing “zapped my screen” (which resulted in a web search) and then eventually heard “zap ice cream,” and—bizarrely—pulled up a Dairy Queen in Beulah, North Dakota.  I’m not kidding.

Since screen snapshots are really useful to bloggers, I kept trying:  “Hey Siri, take a screen snapshot.”  To my great surprise, Siri didn’t play dumb, but simply refused:  “That’s beyond my abilities at the moment.”  Huh?  No way is this beyond her abilities.  I managed to learn (no thanks to Siri) how to get a snapshot (pressing two far-flung buttons at once).  So it can be done.  Why can’t Siri do it?  Is she a bit ... simple?

You may be wondering how I know so many cool Moto commands.  It’s because you can say, “Get a list of commands,” and Moto provides one.  I told Siri, “Get a list of commands” and though—as you can see—she did hear me right, she decided just to show me a map of the nearest Coast Guard station.  WTF!?



Is Siri the best at anything?

Okay, I’ve been pretty harsh on Siri here.  Is she better than Moto at anything?  Well, yes.  I think her navigation is better.  I just asked Moto, “Where is the nearest pizza place?” Moto replied, “Here are the listings for ‘nearest pizza place’ within zero point eight miles.”  The nearest place—Gioia Pizzeria—was listed first among non-paid entries, but at the top of the screen was an ad for Little Caesars $5 Pizza, which a) isn’t nearby, and b) isn’t even pizza.  (I don’t know what that stuff is, but it ain’t pizza.)  Meanwhile, if I were trying to get this answer without having to look at my phone—like, if I were driving—this written response would be useless.  (At least Moto did better than when I first blogged about this, when it lied and said Zachary’s Pizza was the closest.)

Here, Siri did better.  She replied, aloud, “The nearest one I found is Gioia in Berkeley, which averages 4½ stars and is inexpensive.  Would you like to try it?”  Presumably if I’d said yes, she’d have navigated there.  Instead I said, “Actually, Siri, it’s pretty expensive.”  To which she replied, “I’m sorry.”  Well played, Sir[i]!

It’s in the realm of a more specific request where Siri really shines.  I asked, “Where’s the nearest deep dish Chicago style pizza place?”  She showed me Zachary’s, which is correct.  I’m pretty impressed, especially since when I asked Moto the same question, it showed me Giordano’s and Lou Malnati’s, both of which are in Chicago.  As you can see, Moto clearly heard “nearest” correctly, but somehow missed my meaning.


The second really lame thing about iPads

Earlier I complained about how you have to plug in the iPad to get voice activation, and promised to reveal another huge shortcoming.  I doubt you’ll immediately grasp how lame this next one is, but here goes:  Apple iOS doesn’t support the Dvorak keyboard layout, which is  more efficient than QWERTY and has been supported by Apple since the Apple IIc.  According to Wikipedia, the IIc  “had a mechanical switch above the keyboard whereby the user could switch back and forth between the QWERTY layout and the Dvorak layout.... The IIc Dvorak layout was even mentioned in 1984 ads, which stated that the World’s Fastest Typist, Barbara Blackburn, had set a record on an Apple IIc with the Dvorak layout.”
                                                               
I haven’t been able to find anything on the Internet about why Apple decided not to support Dvorak on the iPad.  I guess the default answer for their product choices—“Because we’re gods, and we can do whatever we want!”—will have to do.  It’s so frustrating, since this has got to be really simple to do in software.  It would probably take some Apple developer about five minutes.

But why should you care, since you type on QWERTY anyway?  Well, consider the security ramifications of encouraging third party developers to create such fundamental utilities as keyboard software.  After installing Fleksy, a free Dvorak-enabled app, I messed about with the iPad a little, wandered off to do something more useful, and then realized, “Duh, I’ve just done something really stupid.”  What better way to steal somebody’s keystrokes than to create an app that quite obviously has access to everything I type?

At first I told myself this was no big deal.  After all, I’m mainly using the iPad to browse the web, and I don’t kid myself that my every move on the Internet isn’t already tracked, and not just by the NSA.  (By the way, keep up the good work, guys!  Thanks for keeping me safe!)

But of course, there’s the little matter of passwords.  I felt like I’d just given away the keys to the kingdom, or at least to the two websites I’d logged into (my bank and my e-mail).  I was all set to go change those two passwords, but first decided to see how hard it is to switch iPad keyboards on the fly, so going forward I could type passwords with the native Apple iOS keyboard.  Perhaps there would be a function key right on the soft Fleksy keyboard to simplify this switch?  And then I noticed this:



It might be hard to tell, but in the first snapshot above, the cursor is in the Username field.  In the second snapshot, the cursor is in the Password field.  The same flag that tells the OS to obscure the password (i.e., showing ******* instead of what’s typed) tells the iPad to switch to the standard Apple iOS keyboard.  So those passwords I typed before? I’d typed them on the standard QWERTY  keyboard without even realizing it.  Those passwords weren’t at risk of being intercepted by the Fleksy keyboard app after all.  That’s pretty clever of Apple, isn’t it?

Of course, when your cleverness only serves the mitigate the downside of your pointless shortcoming, it’s actually a lot less impressive.  Hey Apple, why not support the Dvorak layout to begin with, like you did with the Apple IIe, the Apple III, the Macintosh, the Quadra, the PowerBook, the Performa, the iMac, the iBook, and the MacBook?

At the time of this writing, Apple is sitting on over $200 billion in cash.  Couldn’t they spend a few bucks to match the features of their own earlier products?  Hell, they could probably get an unpaid intern to do it.  I, for one, am not feeling the love ... even if Siri does claim to respect me.

Saturday, November 22, 2014

Down With Convenience!


Introduction

“I appreciate the seamless ease….”

That statement is the inspiration for this post.  It’s from a letter a friend wrote me recently.  The point isn’t that he sounds like a TV ad (from the days when ad spokesmen were earnest instead of arch). The point, rather, is that I found this simple statement oddly inflammatory.  I asked myself why.  And the answer is, I should find it inflammatory, and so should you.  Ideally, all my friends would join me in mounting a War on Convenience.  If I can’t have that, well, maybe I can influence a few readers.

A paradox

Of course I was being bombastic and hyperbolic a second ago.  Who doesn’t want convenience in his life?  But I think convenience is like alcohol:  it should be enjoyed responsibly.

Paradoxically, my worldview straddles two seemingly conflicting ideals:  I’m a great lover of efficiency, but I bristle at society’s infatuation with ease and expedience.  “Wait,” you may ask, “aren’t efficiency and convenience pretty much the same thing?”

Nope.  When I say “efficient” I mean that I can get something done exactly how I want it done in as little time as possible.  (Often this involves doing a lot of work up front, like creating macros for a software application.)  When people talk about seamless ease, they’re often referring to systems that are merely intuitive, such as a user interface that can be grasped quickly, without any need for help menus or a manual.  Some products are convenient because they remove tedious steps; other products are convenient because they rescue you from having to learn something.

I think it’s widely assumed that where user interfaces go, intuitive is best.  But this isn’t always true.  Consider the computer keyboard:  to be maximally intuitive, its keys ought to be placed in alphabetical order.  That would make it easier for the first-time user, wouldn’t it?  But of course this idea seems silly, since typing efficiency is more important than making the keyboard layout straightforward for the newcomer.

What’s even sillier is that the QWERTY layout was actually designed to be maximally inefficient, to keep early typewriters from jamming.  The Dvorak layout I use was difficult to learn, but my long-term gains in efficiency were well worth the trouble.

Low-lying fruit

The simplest argument against the embrace of convenience is that it often requires us to forsake quality.  I give you microwave popcorn:  it’s certainly easy to make, but a) it literally stinks, b) it’s more expensive than traditional popcorn, c) it tastes pretty bad, d) it’s full of salt and fat, e) it’s full of chemicals, and f) the excessive packaging is bad for the environment.  The popularity of microwave popcorn makes me embarrassed to be a member of the human race, considering that an air popper is also extremely easy to use, and cheaper, and lets you control how much salt and butter you add.

Whipped cream in an aerosol can is also really convenient, but it’s more expensive and less tasty than what you whip at home, and has the added problem of unpredictability:  it’s hard to tell when the can is low on cream (or non-dairy “kreme” as it often is), so you never know when you’ll foul up your sundae with the liquid dribble that comes at the end.  By whipping my own cream, I can choose an organic product; whip only as much as I need; control the amount of sugar; and save money.

But enough of these convenient examples.  I want to get into the more subtle ways that, through our love of convenience, we sell ourselves short without even realizing it.

The problem of control

Often, complicated systems are made more intuitive, and sometimes more efficient, through a simplification of the user interface and/or automation of repetitive operations.  A little Cessna surely has a simpler interface than a commercial airliner, though it often lacks that handy autopilot feature.


Automation is a fine idea in theory, but in practice, it’s only as good as its execution.  How accurate are product developers’ guesses about what should be automated and how?

Well, here’s a horror story.  My family was visiting some friends in their lovely, sunny home in London.  One afternoon, when our friends were out, I thought, hey, my mother-in-law is always asking for a nice photo of my wife and me.  And here we had this great lighting, so I suggested to my wife that we finally take the time to shoot a nice photo together.  My wife has a tendency to close her eyes in photos, so it took us at least a dozen tries.  Well, on the last day of our visit, our host said, “Hey, why not give us some photos of your visit from your SD card?”  Great idea!  So I took the card up to their Mac and stuck it in the card reader, expecting that I could cherry-pick the best photos of both families.  But to my surprise the operating system seized control, copied every photo off the card, and launched a little slide show, set to music.  This might have seemed really helpful to a novice computer user who hadn’t mastered file management software, but I was appalled.  The software must have chosen to show the pictures in reverse chronological order, because the first two dozen shots were of my wife and me.  We came off looking like the biggest narcissists you’ve ever seen.

Probably there’s a way to tell the Mac not to automatically grab all the photos from an SD card.  But some systems don’t give us a choice.  We consumers often put up with this lack of control because we enjoy the convenience of the overall product.  I see this problem most frequently in Internet-based systems, particularly when the revenue model is more complicated than “you pay me directly for goods or services.”  Things are automated with more than just the user’s experience in mind.

Here’s an example:  the Gmail Adsense engine, which automatically produces custom ads based on my e-mail text, doesn’t exist to serve me.  Were I given the choice to opt out of Adsense, I certainly would.  I don’t even use Gmail, and yet (as detailed here) my e-mails to Gmail users nevertheless produce these tailored ads I like it or not.

But you know what’s even worse than that?  It’s when we’re unaware of how convenience is costing us.  Consider LinkedIn:  it’s very convenient, and a great idea, and I’m glad that it’s free.  But as I’ve only recently discovered, LinkedIn does what it pleases with the information I give it.  Awhile back, because my profile photo was like five years old, I put up a new one.  (The idea was anti-vanity:  I didn’t want people to think I was using an old photo just to look younger to the world.)  To my embarrassment, LinkedIn contacted my 400 contacts on my behalf:  “Dana Albert has a new profile picture!”  As in, “Dana Albert, devoted curator of his own image and his self-important notion of an Albert ‘brand,’ wants you to see his latest self-portrait!”  A few people responded, perhaps snidely, “Nice picture!”  How embarrassing.  (Yes, I am easily embarrassed.  What can I say … I’m an introvert.)

But that’s not all.  I’ve come to find out that LinkedIn evidently does something special for their newer users:  they send an update anytime one of the user’s contacts has made new connections.  Since I don’t get such updates, I’d never have known about this behavior, except a couple of friends commented.  (“Wow, I’ve see a lot of LinkedIn updates on you lately … did you lose your job or something?”)  Once I looked into it, I figured out how to change these settings, but it wasn’t easy—which means that those who thrive on convenience will probably just accept the default behavior.  (Surely I don’t need to go into the various ways Facebook has surreptitiously exploited their users’ tastes, preferences, and purchasing data.)

Are your choices my business?

“Fine,” you might say, “Go whip your own cream, and type on your weird keyboard, and shun Facebook, if that’s what floats your boat—but let me do as I please.”  In other words, you might wonder why your behavior is any business of mine.  Here’s why:  other people’s behavior often affects what choices are available to me.

Here’s how that happens.  Because I worship efficiency, I enjoy figuring out how to make a complicated process go quickly—but not everybody enjoys this process, and manufacturers know it.  New products are often targeted at teens and young adults (to build brand loyalty early), so new consumers’ habits can have an immediate influence on industry.  Streamlining a process, modern consumers believe, should be figured out by the manufacturer and baked into the product.  Thus, the focus is outward on the product, rather than inward on the user.  It’s not “How can I get better at this” but “How can this be better for me?”  The “smarter” our products get, the lazier we’re permitted to be.

(Fortunately, schools are still essentially old-school.  If it weren’t for teachers making kids learn math, do you think these kids would bother, given the ease-of-use of smartphone calculator apps?  And yet, once you’ve learned arithmetic, it’s faster to do it in your head.)

The result of this consumer/producer dynamic is that perfectly valid products are often kicked to the curb.  Consider the manual car transmission, aka stick shift:  is it straightforward?  Not very.  Is there a benefit to learning how to work a clutch?  I think so.  After all, a manual transmission offers better gas mileage, and enables me to roll-start the car if my battery is dead.  My mastery of manual shifting impresses the ladies, and enables me to rent a car in Europe.  The popularity, in this country, of automatic transmissions didn’t used to affect me, until that choice became so ubiquitous that some foreign car companies stopped exporting their stick-shift models here.  When I bought my last Volvo, I couldn’t get one with the transmission I wanted.  I had to settle for an automatic. 

(By the way, that bit about impressing the ladies?  Yeah, that was a joke.  Just seeing if you’re awake.)

Another example:  digital cameras.  What a great invention, and yet the camera industry is really suffering.  You know what the number one camera is today?  The iPhone.  It’s easy to see why:  you’re carrying your phone anyway, so why carry another device?  The problem is, phone cameras are not nearly as good as regular digital cameras—even the more humble point-and-shoot ones.  A phone camera takes inferior pictures because the lens is too small and doesn’t let in enough light for non-flash photography in low-light conditions.  Phone cameras also lack a zoom (their so-called “digital zoom” is pure malarkey—cropping masquerading as telephoto).

Look at these two photos.  The first was taken with a $200 Panasonic Lumix point-and-shoot camera.  The second was with a Motorola Droid phone of the same vintage. 



The point-and-shoot photo is much better, and not because I got out a light meter, set the F-stop, adjusted the shutter speed, etc.  It was as easy to snap as with the phone (easier, actually, because there’s way less delay at the controls).  The only convenience I gave up was having everything in one device.

If the camera industry were healthier, I’d have even better products available to me, and at lower prices (due to economies of scale).  Alas, the market for standalone cameras has been strangled by the ubiquity of camera phones—the more convenient choice.

Whom does convenience benefit the most?

Sometimes the person who seems like the most direct beneficiary of convenience-oriented technologies actually isn’t.  Consider the grocery store UPC reader:  it’s very intuitive, and thus perfect for bringing new cashiers up to speed quickly.  It’s also more efficient, but this benefit does not accrue to the cashier, who is paid by the hour.  The system’s efficiency doesn’t mean the cashier gets a raise; it means he or she is easier to replace, and the store can get by with fewer checkout stations.

Now let’s move beyond human consumers and consider other consumers, like cattle.  Being kept in a small stall in a feedlot is certainly convenient for the cow, in terms of her basic need for sustenance.  Of course this diet causes all kinds of trouble for the poor animal, but her well-being was never the point.  The convenience of the feedlot mainly benefits the meat packer.  Since this arrangement translates into lowered operating costs, which can be passed along to the human consumer, it looks like a win-win.  So it is with cheap, high-margin products like soft drinks and sugary cereal.  Needless to say, in the long term this convenience isn’t benefiting the human consumers, either.  The countless Americans who buy junk food and frequent fast food chains are basically backing in to their own feedlot stalls.

Meanwhile, pharmaceutical companies grasp that there’s big money to be made in drugs that treat lifestyle ailments, and doctors prescribe these drugs because doing so is so much easier than trying to get people to exercise and eat well.  Consumers participate in this lowest-price, lowest-effort economic model without an appreciation for its real costs.  The companies at the top in this economy are the direct beneficiaries of our rampant convenience addiction; by indulging it, they introduce a variety of societal ills.  In this regard, convenience is like secondhand smoke.

Convenience and parenting

If you’re a parent who has made it this far into my essay, I doubt you’re the kind who feeds his kid soft drinks, sugary cereal, and fast food.  But addiction to convenience is also present in the most upscale of products.  I’m talking about PCs, smartphones, tablet computers, and Netflix.

It’s more convenient to park kids in front of the TV or PC than to try to get them to help with dinner or with setting the table.  It’s easier to let a kid use his iPad in a restaurant, while his food gets cold, than to teach him how to behave like a grown-up.  So kids and their parents become co-dependents in a family dynamic that ultimately favors no one.

I won’t lie and say I never give in to such temptations.  But when I do, I don’t pretend I’m being a good dad.  “Shall we sit our kids down in front of a video and let them rot their brains out, just to get them out of our hair?” I’ll ask my wife.  And I’ll say to my kids, “Would you like to put in a video and let your brain be automatically extracted?”  This raises awareness and may help us fend off bad habits.


Do modern kids have the mental space required to daydream?  I’d guess a lot of them don’t.  So when my kids complain that they’re bored, I say, “Good.  It’s good to be bored.”  Necessity being the mother of invention, boredom is a good problem for the mind to solve.  Solving this problem with a library book, a blank piece of paper, or some random household detritus doesn’t do much for the economy, but the economy is not my problem.


“But wait,” you may protest, “Computers can be very educational!”  Yes, they can, but that doesn’t mean just any computer-based activity is intrinsically useful.  Too many parents pretend their Internet-addicted kid might become the next Mark Zuckerberg—because this fiction is more convenient than fighting with the kid about limits on his or her screen time.

My wife and I are all about limits.  This is why we don’t have cable, our kids don’t have phones or tablets, and their PC time is closely monitored and rationed.


“Okay, fine,” you might say, “You’ve identified some troublesome trends, but how are the habits of other families any of your business?”  Well, where the hell are my daughters going to find husbands?  My kids won’t settle for a passive, inert, pasty, video-addled mouth-breather who doesn’t read.  Meanwhile, the boys out there won’t settle for out-of-touch, pop-culturally illiterate nerds who don’t even text.  Sure, there are some boys out there whose parents are just as socially unconventional as my wife and me, but it’s a small pool.

Call to action

If you disagree with all of this, that’s fine—and I thank you for at least reading it.

On the other hand, if you agree with me, you may wonder what I propose to do about this rampant convenience addiction.  The answer is simple (though not easy).  Next time you appreciate the convenience of something, ask yourself if that convenience came at any great cost to you:  to your privacy, to your health, to your family, or to the environment.  Then ask yourself if it’s worth it.  I’ll keep on doing the same.

And at a minimum, if you find yourself using the phrase “seamless ease,” please don’t say it like it’s a good thing.

Wednesday, June 24, 2009

The Case Against Margolis & Liebowitz

The Defendants

I type a lot. In 2002, plagued by hand and wrist pain and fearful of developing a repetitive stress injury, I decided to switch to the Dvorak keyboard layout. Dvorak is an alternative to the traditional QWERTY keyboard. It is named after its creator, August Dvorak, who designed it for maximum efficiency. The QWERTY layout, meanwhile, had originally been designed to keep early typewriter keys from jamming. Unlearning QWERTY and learning Dvorak was very difficult (I’d tried to convert years before and had failed), but since I successfully made the switch I’ve never suffered hand and wrist pain again.

Naturally, I’d like to encourage others to adopt this layout, and I take up that challenge in another blog post. I know from experience that Dvorak is more efficient than QWERTY, and that its benefits justify its learning curve, but I don’t expect to be taken as much of an authority. So, I did a little web research looking for studies of its efficiency. In doing so, I kept coming across an aggressively negative article about Dvorak by a pair of economists.

Right away I was nonplussed: what were economists doing studying typing efficiency in the first place? The answer is, these two take an interest in Dvorak because it is the poster child for an economic theory they refer to as “lock-in,” which is the (alleged) ability of inferior products to command inappropriate market share. The “lock-in” debate concerns the extent to which factors other than a product’s performance, such as an early foothold in the market or strong-arm market practices, can largely shape the competitive landscape.

Other classic examples of this economic theory are gradually losing their punch. For example, the Apple vs. Microsoft case study has become less relevant, as the obvious inferiority of MS-DOS to the Mac OS has given way to the arguable similarity of features between Mac and Windows. Or take the case of Betamax vs. VHS: once the source of lively debate, both video formats have become historical footnotes given the rise of the DVD. In contrast, the durable near-ubiquity of the QWERTY layout remains, justifiably, the perfect example of how performance and inefficiency can continue to take a backseat to sheer societal inertia.

The evil of two lessers

For philosophical, intellectual, and political reasons, Liebowitz and Margolis don’t like to accept that lock-in is a legitimate economic theory. I suppose they prefer to believe that the free market can solve all problems; in any case, it is essential to their position that Dvorak be discredited. So, despite the fact that they dwell in the abstract realm of economic theory instead of the literally hands-on physical realm of human/machine interfaces, they position themselves as authorities and assail the Dvorak layout with gusto in their article “The Fable of the Keys” in the Journal of Law & Economics, and (in shortened form) in their article “Typing Errors” in the June 1996 edition of Reason magazine.

“Typing Errors” article is pretty well written. It’s glib and polished, and the uncritical lay reader can be forgiven for being swayed by it. Even the normally unflappable Cecil Adams of The Straight Dope, after initially decrying the inefficiency of QWERTY, was taken in by “The Fable of the Keys”, falling on his sword and disavowing the entire content of his original article.

On closer inspection, however, Margolis and Liebowitz’s paper turns out to be poorly researched, and its arguments weakly constructed. The article has two fundamental problems. For one thing, the authors’ critique is targeted mainly at existing efficiency studies of the keyboard, rather than at the keyboard itself. Bad studies don’t mean a bad keyboard! Meanwhile, their article is far too focused on the feasibility of retraining QWERTY typists on Dvorak, not the ongoing benefits of the Dvorak layout once it’s been learned. The difficulty of retraining is beside the point: we don't need today's typists to unlearn QWERTY and learn Dvorak—we need tomorrow's typists to learn Dvorak to begin with.

A brief examination of these two fundamental flaws ought to be enough to thoroughly discredit the Margolis/Liebowitz thesis. But I won’t stop there. Because these hotshot economists have published a crappy article in a highly regarded journal, and because their quest to make an arcane point about economics has added to the inertia that prevents widespread adoption of a useful innovation, I aim to systematically dismember their argument to expose the full range of its flaws. Yes, your unsung blogger will take on the fancy eggheads using nothing more than logic and first-hand experience.

Red Herrings

The Margolis/Liebowitz argument begins with a section called “Tainted evidence for Dvorak.” They argue that Dvorak’s own study wasn’t subject to sufficient controls; they describe, for example, how Dvorak “compared students of different ages and abilities (for example, students learning Dvorak in grades 7 and 8 at the University of Chicago Lab School were compared with students learning QWERTY in conventional high schools).” After dispatching the large body of August Dvorak’s work in a few paragraphs, they proceed to a Navy study about the Dvorak layout. They find flaws with the Navy study as well: for example, “The participants’ IQs and dexterity skills are not reported for the QWERTY retraining group.” They cite differences in the study’s methods of measuring performance between the two layouts. They point out that August Dvorak, a Navy man, was the top expert in the Navy study. Margolis and Liebowitz present this last bit like it’s some sort of a conspiracy, and decry the fact of August Dvorak’s financial stake in the design.

Most of these grievances seem pretty nit-picky to me. The quality of the schools in the study wouldn’t seem to be a big deal, since plenty of people learn to type using simple software. (I learned Dvorak using a very basic website.) The lack of IQ benchmark strikes me as laughable; after all, Stephen Hawking, one of the foremost minds of our time, can’t type for beans. (Note to Margolis and Liebowitz: if you’re reading this, which I truly hope you are, please don’t build your rebuttal around that statement—it was a joke.) The financial interest Dvorak had is a bit more troubling, but don’t companies routinely fund their own performance studies? This is called marketing. (“Your mileage may vary.”)

But fine, let’s give these two the benefit of the doubt. Let’s assume that both the Dvorak study and the Navy study were complete frauds, conducted by deranged, dog-kicking sociopaths whacked out on coke and smack. Does that mean the Dvorak design isn’t more efficient? Of course not. Osama bin Laden could publish a pack of lies about the Dvorak design tomorrow, and it’s not going to make me type any slower.

Narrow interpretation

The next section of the Margolis/Liebowitz article is called “Evidence Against Dvorak,” and focuses on a government General Services Administration study. Margolis and Liebowitz describe the study as “a carefully controlled experiment designed to examine the costs and benefits of switching to Dvorak.” The ten subjects of the study took “well over 25 days” (whatever that means) to catch up to their old QWERTY speeds, after which their progress slowed. Meanwhile, a control group of QWERTY typists showed greater ongoing gains in speed than the Dvorak group. Based on these results, the director of the study concluded that “Dvorak training would never be able to amortize its costs.”

Is this really evidence against Dvorak? Note that the goal of the study wasn’t to assess the actual efficiency of Dvorak compared to QWERTY, but rather the merit of retraining QWERTY typists at government expense. The conclusions of the study itself, meanwhile, beg a lot of questions:

  • Is twenty-five days really an unreasonable amount of time to unlearn an automatic, unconscious skill and learn a new one? In other words, is it not possible that the study was ended too soon? (My own speed continued to increase for years after I learned Dvorak.)
  • Is speed the only measure of the validity of a keyboard design? Did anybody bother to ask the participants which keyboard was easier on their hands and wrists? Were the long-term costs of repetitive stress injuries even considered?
  • Is ten typists a large enough sample?

Margolis and Liebowitz go on to narrowly interpret the results of other studies. They cite a 1973 study of six typists that found that after 104 hours of Dvorak training, typists saw a 2.6% increase in speed. I take this as evidence for, not against, Dvorak given that, by my own rough calculations, I will spend around 45,000 more hours typing by the age of seventy. A mere 104 hours of training, after which my hands and wrists stop hurting, seems like a good investment to me. This 1973 study is only “evidence against Dvorak” because Margolis and Liebowitz label it as such.

Meanwhile, a fundamental difference between Dvorak’s own study and these others is that Dvorak assessed the ease with which children learn the Dvorak layout, and the children's ultimate results thereafter. He was looking to a future generation unhindered by the need to unlearn an obsolete keyboard layout. The “Typing Errors” authors don’t seem to appreciate this difference in approach, framing the debate only in terms of the difficulty of retraining.

More red herrings

From here, the Margolis and Liebowitz spend one brief paragraph referring in the most general terms to other works denying the validity of Dvorak. They cite “other studies” without naming them, and conclude “The consistent finding in ergonomic studies is that the results imply no clear advantage for Dvorak.” What ergonomic studies? Whose findings?

I wouldn’t dwell on this vagueness so much if Margolis and Liebowitz didn’t then proceed to blather on for eight long paragraphs, in their section titled “QWERTY’s competition,” about competing early typewriters that lost out to QWERTY in speed tests back in the 19th century, decades before the Dvorak layout came into existence. Margolis and Liebowitz conveniently neglect to mention that the only record that matters—the current speed record—was set on a Dvorak keyboard, with a words-per-minute rate of 212, significantly faster than anything anybody has done on a QWERTY. (See for yourself: http://www.answers.com/topic/typing; search within the page on the text “Blackburn.”) I find it absurd that these two economists see fit to so smugly discredit the validity of early Dvorak studies when their own research ignores any typing records set after the year 1889.

Hubris

The economists, apparently drunk on their own bathwater, go on to boast that “we published a more detailed version of this material in a Journal of Law and Economics article titled ‘The Fable of the Keys.’ This journal is well known and has published some of the most influential articles in economics. In the six years since we published that article there has been no attempt to refute any of our factual claims, to discredit the GSA study, or to resurrect the Navy study.”

These guys shouldn’t confuse widespread apathy on the part of their readers with tacit agreement. The fact is, their readership is almost entirely comprised of entrenched QWERTY users who aren't in a position to judge Dvorak for themselves. If Margolis and Liebowitz wrote an equally poor paper about, say, childbirth not actually being that painful, you can bet they’d meet with plenty of dissent. (Meanwhile, a month after Margolis and Liebowitz made this boast, Reason magazine—the publisher of “Typing Errors”—received, and printed, a scathing rebuttal to the original article.)

Speaking of dissenting opinions, where are the successful Dvorak converts in “Typing Errors”? Did Margolis and Liebowitz’s research not manage to find any? It’s actually not hard to do. I checked out an opinion piece in the New York Times and found fifteen comments (not counting my own) posted by happy Dvorak converts. Okay, not a huge number of people, but it’s just one website; besides, the GSA study—Margolis and Liebowitz’s centerpiece—had even fewer. And any one of us Dvorak converts has a legitimate real-world perspective on the merit of the Dvorak design, which strikes me as a lot more valid than an argument based solely on the available literature of others. (Would Margolis and Liebowitz refute the benefit of the two-button computer mouse just because reams of scientific performance data aren’t available to substantiate its utility?)

Conclusion

“Typing Errors” assumes that the merit of a product design can be creditably evaluated solely on the basis of existing literature. Its authors ignore obvious questions, such as how a layout like QWERTY, designed decades before the advent of touch-typing, could possibly be as efficient as one designed with touch-typing in mind. They apparently fail to notice the obvious failings of QWERTY, such as the scattering of indispensable vowels across the board with the lowly semicolon getting a prime spot on the home row. They’re looking at decades-old studies instead of at the keyboard they’re typing on.

This article should serve as a cautionary tale about the perils of making up your mind in advance of your research, and tailoring your interpretation to suit your thesis. It’s a real pity that the quest of a couple of academics to make an arcane point about economics has managed to mislead the public about something more important. Economic theory aside, Margolis and Liebowitz are hindering the adoption of a technology that can offer tangible benefits.

The Case for Dvorak


National Safety Month

As you may know, June is designated as “National Safety Month” in the U.S. by the National Safety Council. Perhaps it’s no coincidence, then, that I stumbled across two separate news stories the other day covering the same strange topic: acute computer-related injuries. An ABC news story warns readers that “computers are not play toys” and cites the risks of crushing, strangulation, and electrocution, though it also concedes that the percentage of ER visits due to PC injuries was just 0.008 percent. The other story, citing a different study, finds that more than 21 percent of injuries documented were from computer equipment falling on a person.

Slow news day, huh? But accidents aside, isn't there a much bigger story about the physical danger posed by PCs? I'm talking about repetitive stress injuries, the elephant in the room that these journalists evidently decided to ignore. And why? It's a serious problem. My wife recalls from her journalism days that half the copy editors in the news room wore wrist braces at least some of the time. Think of your own experience and talk to your friends and colleagues: who has had hand or wrist pain from typing, vs. who has had a PC monitor fall on his head?

Lawyers Cash In



Chances are good that you've had a laptop or keyboard with a little disclaimer sticker on it: “WARNING: To reduce risk of serious injury to hands, wrists, or other joints, read Safety & Comfort Guide.” (Never mind that in this photo it’s on my stapler. I moved it.) This disclaimer stems from a 1996 lawsuit in which Digital Equipment Corporation was successfully sued and forced to pay $6 million in compensatory damages to three office workers who developed repetitive stress injuries from using DEC keyboards. Why was DEC singled out, when any keyboard could have caused this injury? It’s because they'd trained their own employees on the dangers of typing but hadn’t warned their customers.

The lawyers on that case must have been pretty slick. But imagine that you're a lawyer pursuing similar litigation and could show the following:
  • This equipment corporation was using an ancient keyboard layout specifically designed to be inefficient, to keep 19th century typewriters from jamming;
  • Instead of thinking of customer safety, a silly marketing gimmick—the ability to spell the word “typewriter” using only the top row of keys—was a design goal of this layout;
  • The corporation declined to offer a more efficient keyboard layout even though one has been available since 1936.
All of these statements are true, but in practice would be of no use to a lawyer because no mainstream keyboard manufacturer offers the more efficient layout—that is, no single corporation is uniquely guilty here. Alas, the so-called “QWERTY” keyboard you’re sitting in front of right now is the very 19th century design I’ve described above. A lawsuit founded on the QWERTY’s lack of efficiency would have to be filed against an entire industry—no, actually, against an entire society—for tolerating this state of affairs. In short, I believe that QWERTY, not DEC or any corporation, is the real villain with regard to keyboard-related repetitive stress injuries.

Battling a legacy of lameness

People have been historically dense about typing efficiency. The typewriter wasn't originally introduced as a way to write faster—just to be more legible. In fact, the widespread practice of touch-typing came more than fifty years after the typewriter was invented. For the first fifty years, most people just hunt-n-pecked!

I first became aware of the existence of a superior keyboard layout in the mid-eighties when I saw the Guinness Book of World Records certified fastest typist go up against the “Late Night With David Letterman” secretary in head-to-head competition. Letterman turned the race into a farce by breaking whatever promise he’d made to the record-holder to provide her with the special typewriter she needed. Instead, just for laughs, he set her up on a QWERTY machine, and declared her a fraud on the basis of her having typed pure gibberish. The poor woman was almost in tears. I could tell something was up, because typing gibberish is actually no faster than typing actual text. (Try it!) I realized this record-holder must use a more efficient layout, and I was intrigued.

Somewhere along the line, I learned more about this alternate keyboard layout. It’s called Dvorak, was created in 1936, and is named after its creator, August Dvorak. He researched typing efficiency for years in developing his design, placing the most commonly typed letters in the most convenient places, and putting all the vowels on the home row under the fingers of the left hand, so that the two hands alternate as much as possible. The fact is, his layout wouldn’t need to be the most efficient possible to be a big improvement over QWERTY. If he’d done a merely passable job with his layout, it would be a big step up given the design intent of the original. Just knowing this more efficient layout existed, I decided I had to try it. Here’s what the keyboard looks like:


A False Start

In January through June of 1995 I tried to learn Dvorak and failed. Windows PC software didn’t support Dvorak yet so to use it I had to remap every key on my keyboard. I already had a macro-programmable keyboard that made this possible, and by sheer luck I had the same keyboard at work. But I had problems. For one thing, the keyboard would occasionally lose its mind, turning my typing into gibberish and requiring me to painstakingly remap the keys all over again. But more importantly, my approach to learning Dvorak, I think, was all wrong. I figured I’d learn it at home and then start using it at work. But all the QWERTY typing I did at work was undermining anything I could learn at home. Because touch-typing is an automated process—your fingers do what they’re supposed to without explicit, conscious instructions from the brain—you have to unlearn QWERTY before you can learn Dvorak. At least, I did.

My personal philosophy is that when you know what you ought to be doing, you should just do it—excuses are no good for the soul. In keeping with that philosophy, and because I was using a PC eight to ten hours a day and my hands and wrists ached every evening, I decided I had to get past QWERTY. I finally tackled the Dvorak project again in March of 2002, shortly after reading an inspirational article. By this time, Windows software had Dvorak support built in (Apple had supported it since the ‘80s). I decided to take the cold-turkey approach, converting my home and work PCs to Dvorak and vowing never to go back.

Success

Right after making this resolution I was tasked at work with writing a proposal that ran a couple hundred pages. I was of course tempted to postpone my Dvorak project, but decided any excuse would just breed others, and made up my mind to forge ahead on the alternative keyboard layout. I’ve heard that learning happens faster under duress, and perhaps it’s true: by the time that proposal was done, I was touch-typing on Dvorak. I wasn’t going very fast (maybe thirty or forty words per minute), but my speed has steadily increased ever since. According to an online speed test I just conducted, I’m typing on Dvorak at ninety words per minute, about five words per minute faster than I had after twenty years on QWERTY. More importantly: despite typing more now than I ever have in my life, I never have hand or wrist pain anymore. Never, ever. Dvorak is the real deal.

Why you will reject this innovation

I would be very surprised if anybody switched to Dvorak on the basis of this blog. First of all, I’m not so sure anybody reads this. Second, you are all weak. Okay, I’m kidding. Actually, I think there are a good many reasons why improvements in product efficiency fail to gain widespread adoption. In this essay I will explore some of these reasons, and their applicability to the Dvorak case in particular.

There are probably endless reasons why useful innovations fail, but I’m going to focus on four of them. Here are what I see as the most common low-adoption pitfalls:
  1. What’s in it for me? The precise gain in efficiency is difficult to predict or understand.
  2. The mixed bag. The gain in efficiency is offset by other decreases in overall functionality.
  3. Aesthetics & cultural signals. The revamped product is inferior aesthetically and/or is nerdy.
  4. Don’t go changing. The revamped product requires up-front work and/or behavioral change that scares people off.
(Yes, this is going to be a long article. I’m sure you have something better to do, like watching “American Idol.” Go right ahead. But if you do, all you’ll have to discuss tomorrow at the water cooler is “American Idol,” and all you’ll have to discuss during your retirement is how much your arthritis sucks. And I’ll be the smug guy in the nursing home making fun of your wrist braces.)

Low-Adoption Pitfall #1: What’s in it for me?

It’s hard to commit to a product innovation solely on the grounds of its supposed increase in efficiency. When the product’s performance is—or seems to be—measurable in simple numbers, people are easily persuaded to upgrade. If a 1 GHz PC processor is fast, why, 2 GHz must be twice as fast! If a 7.2 megapixel camera takes sharp pictures, 10 megapixels must be even sharper! Whether or not the numbers translate into actual benefit, people don’t need much convincing. But it’s harder when numbers aren’t involved, or when you don’t have a sense for how your existing product stacks up to the latest and greatest.

Take, for example, your refrigerator. According to the website p2pays.org, this appliance uses a sixth of all the electricity in your home. But how much of that electricity could you save by upgrading? Well, that depends on how old your existing refrigerator is, and what you’re replacing it with. P2pays.org tells me a new fridge could save me up to $94 a year—but what assumptions are they making about what I’m starting with? Stopglobalwarming.org suggests that a new fridge will save me $60 a year, but they don’t provide their assumptions either. A Cornell University study says a ten-year-old fridge uses twice as much electricity as a new Energy Star fridge, but they go on to list actual annual consumption numbers (690 kWh and 436 kWh, respectively) that belie their “twice as much” statement. After awhile my eyes glaze over, and through sheer inertia I stick with my old fridge.

Low-Adoption Pitfall #2: The mixed bag

Many innovative products solve one efficiency problem while introducing others. Perhaps the new problems struck the innovator as mere idiosyncrasies, or perhaps the new problems don’t bother everybody. I can think of several examples of this mixed bag scenario.

First, I give you the recumbent bicycle. I believe it is well established that these bikes are more aerodynamic than a traditional bike, especially if they have a full or partial fairing. The world record for human powered travel was set on a recumbent, and probably the next ninety-nine runners-up were recumbents as well. But the bikes are heavy, so they’re slower going uphill, and they have too long a wheelbase to corner quickly, and they’re not very stable on downhills. They’re also less visible to cars, and hard to mount on a car rack or take on the train. For most riders, the increase in efficiency on flat, straight roads isn’t enough to overcome the disadvantages.

I can think of other examples of mixed-bag innovations: the digital car speedometer (harder to read at a glance), the electric can opener (loud, takes up counter space), the car alarm (makes everybody in the vicinity rightfully wish for your death), and the Kindle (which, being an electronic device, denies its user the escape from electronic devices that is one of the great pleasures of books). I suppose these aren’t all classic cases of failed products, but they’re not runaway successes either.

Low-Adoption Pitfall #3: Aesthetics & cultural signals

We need look no further than the ongoing popularity of the stiletto heel to remind ourselves that efficiency and performance aren’t everything. Aesthetics can—and should—be a consideration when we decide whether or not to adopt a product innovation. Take the case of digital watches: they’re loaded with features—some of them actually useful, like an alarm or a backlight—but I for one am glad they haven’t replaced analog watches. That doesn’t mean I fault you if you prefer digital; I’m just glad I still have a choice. We humans have to look at consumer products all the time; they might as well look good.

In some cases I think we as a society have a real responsibility to reject innovations on aesthetic grounds even if the increase in efficiency is obvious. I give you the modern plastic squeeze bottle of ketchup. Just look at it, compared to its vastly superior ancestor:


It’s almost as though the newer bottle is designed to reflect the physique of the modern American: short, squat, and fat. And of course the new bottle dispenses the product much faster than the old one; instead of the subtle air-bubble-sliding technique, the consumer can now force the ketchup out as fast as he wants. The squeeze bottle even makes a fitting flatulent sound as it spews. Revolting. And yet the American consumer seems to have rolled over on this one: I haven’t seen a proper glass ketchup bottle in a store in years. (Here’s a tip: next time you’re in a decent restaurant or diner, all you have to do is use up all the ketchup in the glass bottle at your table. The label says “Not for resale” and “Do not refill.” On these grounds you can ask to be given the empty bottle, with reasonable expectation of success.)

Along with purely aesthetic considerations, we shouldn’t ignore the cultural signals that our product choices can send. Returning to the case of the recumbent bicyclist, it’s pretty obvious that—whether his turtle-on-its-back position strikes you as inelegant or not—he’s clearly an iconoclast, his odd choice of steed a tacit rebuke to the rest of us. To put it bluntly, the nerd factor of a recumbent is very high. Other high-nerd-factor products include the pocket protector (not in itself particularly ugly, at least no more so than a modern ketchup bottle) and its modern-day equivalent, the smartphone belt holster. I’m not real fond of Bluetooth earpieces, either.

Low-Adoption Pitfall #4: Don’t go changing

Consumer product upgrades are especially compelling when the only thing the consumer has to do is pay his money, following which the increase in performance is automatic. If you replace your 25-pound steel bike with a 16-pound carbon fiber one, you’re going to go faster as soon as you start pedaling. But upgrades are a harder sell when the better product requires work on the part of the consumer. I’m cheered by the huge success of compact fluorescent light bulbs, but at the same time I’m dumbfounded that so few of their adopters seem to have ever tried dimmer switches, which have been around for decades. The only explanation I can think of is that people are too intimidated by the prospect of working around live wires to install the dimmer switches, while anybody can change a light bulb.

The hardest sell of all is a product that requires the user to learn a new technique. The most dramatic example that comes to my mind is the 1989 Tour de France stage race, when Laurent Fignon lost the three-week, 2,000-mile race to Greg LeMond by only eight seconds, on a drastically less efficient bike. The big difference was the aerodynamic handlebar LeMond used. With it, he beat Fignon in all three time trials (races against the clock, where the rider must fight the wind alone).

The aero handlebar was nothing new, really; triathletes in the U.S. had been using them for years by this point, and the American 7-Eleven team had been using them in Europe all season. But Fignon, along with the other tradition-bound European racers, didn’t seem interested in this technology, even after losing time to LeMond in the time trials. Given that in head-to-head stages Fignon seemed the stronger rider, shouldn’t he have started to suspect that his traditional bike was holding him back, and switched to the aero bars for the final time trial? Perhaps Fignon just didn’t believe he could adapt quickly enough to the new position these bars required. (Needless to say, after LeMond’s triumph, the entire European peloton adopted the aero handlebar and with a few notable exceptions they’re ubiquitous in time trials to this day.)

Now that I’ve outlined some of the classic reasons an innovation can fail to gain widespread acceptance, I’ll evaluate the Dvorak keyboard with these reasons in mind.

Dvorak and Low-Adoption Pitfall #1: What’s in it for me?

Let’s face it, Dvorak has a pretty big image problem. For one thing, the vast majority of typists have never even heard of it. And those who have probably don’t know exactly what it is. The name doesn’t help; I’ve been typing on this thing for years and don’t even know how to pronounce “Dvorak.” Is it “De-VOR-ack,” or “De-VOR-zhock?” The word looks foreign and therefore suspicious, and it also summons the idea of wussy classical music. (I actually like the music of Dvorák the Czech composer, but then I’m a bit square to begin with.)

A further challenge: as status-quo-challenging innovations go, the Dvorak keyboard layout doesn’t have any heroes behind it. Its creator was an obscure educator who stayed obscure. To return to the handlebar anecdote: Greg LeMond was an American hero who won, three times, one of the biggest sporting events in history. Surely he more than anyone is responsible for the aero handlebar’s widespread success. Going back a bit further, let’s look at David and Goliath. When any of the rest of us would have cowered in fear, David went right out and fricking slew the evil giant. What could be more heroic than that? The closest thing Dvorak has to a hero is the Guinness Book of World Records fastest typist—whose moment in the sun, if you’ll recall, was spoiled by David Letterman. (Even if it hadn’t been, how heroic is typing fast, anyway?)

At least now you’re aware that the Dvorak alternative exists. And given that you probably type a whole lot, every day, you might even care that there’s a more efficient option to what you have today. At the same time, you’re entitled to be skeptical about the actual gains in efficiency this newer layout can offer you. Sure, it worked for Dana, but who the hell is he?

The theory behind Dvorak

Before I get to the body of evidence for (and, oddly, against) Dvorak, let’s take a moment to examine the gist of its design differences over QWERTY. There are two main principles at work with Dvorak.

For one, the vowel keys are located beneath the fingers of the left hand, with common consonants under the right hand, to maximize the extent to which the hands alternate when typing a word. (English words tend to alternate vowels with consonants.) Try typing (on your QWERTY keyboard) the following letter sequence: sf sf sf sf. Now try fl fl fl fl. Which was easier? Which was faster? Obviously fl fl fl fl. See? Alternating hands helps. (Of course, alternating consonants like this doesn’t actually help to type real words, so what you’re really seeing here is the lack of this trait on QWERTY.)

The second main principle in Dvorak is that the most commonly used letters in the English are located on the home row, right under where your fingers naturally rest. This decreases the amount of reaching you have to do with your fingers. Try typing a few letters on the home row: sldk sldk sldk. That’s really easy. Now try typing a few letters that aren’t: enoc enoc enoc. That’s a bit harder, isn’t it? To get to the upper row you have to straighten your finger out a bit and reach. To get to the lower row you have to curl your finger toward your palm a bit, which is even harder. In the process you occasionally miss the key you’re reaching or curling toward: a typo.

And yet, these trickier keys to reach—e, n, o, and c—are very common letters you shouldn’t have to reach for. With Dvorak, three of these letters are on the home row. Another example: type “the”—the most common word in the English language—on QWERTY. You start with a long diagonal reach to the upper row with the left index finger, a sideways reach with the right index, and a reach to the upper row with the left middle. Not very efficient. With Dvorak, all three letters are right under your fingertips on the home row. Much more efficient.

The key to QWERTY’s inefficiency

Out of top twenty words in the English language, only two can be typed on QWERTY without leaving the home row, whereas sixteen can be typed on the Dvorak home row. Of the ten most common letters in English, only three of them are on the QWERTY home row, whereas nine of them are on the Dvorak home row. (The ninth most popular letter, “r,” was evidently sacrificed to the cause of getting all the vowels on the Dvorak home row.)

Just stop for a second and stare at your QWERTY keyboard. It’s a mess! The indispensable vowels are scattered across the board, while the seldom-used semicolon gets a prominent spot on the home row. How did they get it so wrong? Simple. It’s a result of the state of the industry when QWERTY was created: the concept of the home row simply didn’t exist back then, because the QWERTY creators never envisioned that people could touch-type. Typing in the year 1872 was a two-finger operation where every keystroke was a reach. In 2009, doesn’t it just make more sense to type on a layout that was specifically designed for efficient touch-typing?

The buzz about Dvorak

What a silly section heading. There’s very little mainstream buzz about Dvorak. We have two very old studies from the 1930s and ‘40s establishing its merit: the original one funded by Dvorak himself around the time he created his layout, and another by the US Navy. Alas, neither report is to be easily found on the Internet. There’s another study, from the 1950s, by the General Services Administration (a government office) that followed the efforts of ten would-be Dvorak converts and concluded that the government should not bother retraining its employees. (I can’t find this online either.) Then there are individuals’ websites, like this one, set up by happy Dvorak users to promote the layout, simply for the benefit of society.

The only modern, formal, published paper you’ll find was written by a pair of economists, Stan Liebowitz and Stephen E. Margolis. Their names pop up every time you research the Dvorak keyboard. I read their paper, and was so annoyed by it that my discussion of its many failings has spawned its own essay: The Case Against Margolis & Liebowitz.”

In the meantime, suffice to say there isn’t much in the way of easily accessible, mainstream, authoritative testimony as to the actual efficiency of the Dvorak keyboard layout. There are testimonies, though, if you hunt for them. I found many among the comments from converts at this New York Times web page. Whether or not you accept up front that Dvorak really is more efficient, we’ve still got three more Low-Adoption Pitfalls to consider, starting with…

Dvorak and Low-Adoption Pitfall #2: The mixed bag

Assuming that Dvorak really is more efficient than QWERTY, we still have to decide if adopting something non-standard is actually worth the hassle. Clearly, there are some downsides to switching to a format that virtually nobody else uses. You may well be intimidated by the process of setting it up to begin with. Beyond that, we all type some of the time on other people’s computers, and there are things we do with a keyboard besides typing simple text, and then there’s the matter of our own computer having all the keys mislabeled.

Setting it up

Converting a Windows 2000 or XP PC to Dvorak the first time is admittedly difficult if you try to figure it out on your own. (With these operating systems Microsoft put keyboard layout options under “Regional and Language Options” instead of “Keyboard.”) But if you follow the explicit directions widely available on the web, this is a five-minute exercise and then you’re done. After that, switching between layouts is easy, with an icon Windows puts on your system tray. And if you employ user profiles on your home PC, you can pre-configure each one with its own layout, so you never need to change anything. (I’m not going to talk about Macs here, other than to predict that their Dvorak support is better than that of Windows, given Apple’s overall OS quality, the fact that they’ve supported Dvorak since the 1980s, and the fact that Steve Wozniak himself types on Dvorak.)

With Vista, Microsoft did a much better job on Dvorak support. (In fact, it’s about the only thing I can see that Vista does particularly well.) A keyboard icon is located, by default, on the taskbar (and a similar one is on the opening login screen):

Switching around

Okay, but what about typing on other computers? Well, you’ll still be able to do it, using QWERTY—the keys are labeled, after all. I can type at about 35-40 words per minute on the old layout, though I never, ever practice on it. (What slows me down is having to look at the keys.) I have to say, during my QWERTY test just now, I had to marvel at how my fingers were going all over the board, constantly reaching for far-flung keys. The difference is not subtle. It’s like the difference between bagging groceries and stocking shelves.
It’s actually very odd: when I first mastered Dvorak, I couldn’t type QWERTY at all, but it’s gradually coming back. Typing on my Blackberry—which I do no more slowly than anybody else—seems to have sharpened my QWERTY skills. Many Dvorak typists can switch back and forth with ease, and I’m gaining confidence that I, too, could develop this ability if I devoted any effort to it.
So ask yourself: how often do you really type in Internet cafés or on other people’s computers? Is protecting your speed on these other computers really worth typing more slowly, with more pain, all the time?

Beyond text

In trolling the web for Dvorak lore I have occasionally come across the argument that not all typing is of text, and that relearning control-character sequences represents a significant hurdle. To me, this sounds suspiciously like something an intransigent QWERTY typist would say. All I can tell you is, it’s no big deal. After all, aren’t those control-character sequences pretty ambiguous to begin with? I’ll grant you that Ctrl-C for “copy” makes sense, but why is Ctrl-V such an obvious assignment for “paste”?

Besides, I still type these same letters—I just do it with different keys, no differently than with text. I configure Cisco routers, using the non-GUI command-line interface, with no problem on Dvorak. (And when I had to take a PC-based Cisco certification exam on a QWERTY, that was no problem either. Well, actually, it was a big problem, but not because of the keyboard.)

What about PC gaming? Okay, now I’ll freely confess I’m out of my depth as I don’t ever play computer games. But, this being a full-service blog, I’ve done a cursory Google search and unearthed a small society of Dvorak gamers. Enjoy!

The little issue of labels

You may be wondering if it bothers me to type on a keyboard on which virtually all of the keys are mislabeled. Actually, this bothers me not one iota. In fact, I purchased my first Dvorak keyboard (for $20) just a few weeks ago, and I never use it. (It’s for my daughter, Alexa, so she never has to waste a single moment hunt-and-pecking on the QWERTY keyboard that she is forbidden to ever use.) The fact is, if you need to look at the keys, you really don’t know how to type! That’s actually good news for you, because it will make learning Dvorak that much easier—you have nothing to unlearn.

I first learned to type on the IBM Selectric typewriter, a gorgeous piece of American engineering. The only thing I didn’t like was that the keys were blank: my typing class in junior high used specially made typewriters. Having blank keys was the only way to ensure that students didn’t look at the keys while trying to learn. It is, I believe, well established that you cannot learn to touch type if you look at the keys. So don’t waste your money on a Dvorak-labeled keyboard or stickers for your laptop keys—you’re better off learning on a QWERTY-labeled board. (This is handy for when somebody borrows your computer, too.)

Dvorak and Low-Adoption Pitfall #3: Aesthetics & cultural signals

Five thousand words into this blog, it’s tempting to dispatch this low-adoption pitfall quickly with the simple argument that there is no aesthetic difference between QWERTY and Dvorak because you haven’t replaced any hardware. The act of typing might look slightly different to somebody who’s paying very close attention, but that’s about it. I do get comments about the sound of my typing, when I forget to mute my phone during conference calls. These comments are always some version of, “That must be Dana. Nobody else can type that fast.” An aesthetic demerit? I think not.

But of course there’s the cultural signaling issue to deal with. Anytime you reject the status quo in favor of something you feel is superior, you run the risk of seeming elitist. (Funny, though, how this doesn’t seem to worry people in the case of expensive cars and designer clothes.) Among those who know I use Dvorak, the responses have been benign, similar to people’s response to my good grammar and early morning workout regimen. That is, it’s treated like a generally harmless idiosyncrasy; I’m a nerd, and probably elitist, and probably no fun to have a beer with, but nothing to get up in arms about. (Actually, I like to think I’m a fine beer-drinking companion.)

It’s probably impossible to keep your Dvorak preference a secret from everybody, though some version of “don’t ask, don’t tell” would probably work just fine pretty well if you’re concerned about it. I wouldn’t put my Dvorak skill on my résumé, and I don’t generally talk about it, and that should be enough. Besides, as I’ll cover in this next section, I wouldn’t actually ask you, the reader, to adopt the Dvorak layout. This blog isn’t about you—it’s about your kids.

Low-Adoption Pitfall #4: Don’t go changing

Perhaps the strongest anti-Dvorak arguments pertain to the difficulty of retraining. Certainly this is the focus of the government General Services Administration study that provided much of the fodder for Margolis and Liebowitz’s polemic (click here for details). I’ll freely confess, unlearning QWERTY and learning Dvorak was really, really hard. There were moments when I’d get brain-freeze and for a split second be unable to type on either layout. It was in the same league, effort-wise, as learning not to cuss in front of my kids.

But the difficulty of retraining is really beside the point. Society has labored under the yoke of QWERTY for 137 years—another thirty or fifty years of it isn’t the end of the world. What’s important is to stop this hemorrhaging of efficiency for the next generation, by teaching the Dvorak layout to new typists. This isn’t a problem of aptitude—it’s attitude. If we can all agree that QWERTY is lame, can’t we take the next step and abandon the self-centered, narrow-minded idea that if it’s good enough for us, it’s good enough for our kids?

Generation gap

This wouldn’t be the first time that a better way of doing things was adopted first by the younger generation. Consider the long-awaited “paperless office.” After an unpromising start, this dream is finally beginning to approach reality. I know this because my colleagues, every time they want to print, are futzing around trying to get their PCs to talk to the LAN printer because they haven’t printing anything in so long. Myself, I inherited a local printer from a laid-off colleague about a decade ago and I’m still on that original print cartridge. The man who hired me had a credenza and a large file cabinet to store his papers; though I inherited these when he left, I’ve barely added to them in the last five years. The amount of work-related paper I’ve accumulated is a stack about two inches thick.

And yet, printing does go on in our office—a fair amount of it. Our printer and copier are in a room adjoining the kitchen, and every time I head in to fill my water or nuke my lunch, somebody is in there collecting his or her print job. And every time, it’s someone with gray hair. I’ve never seen a person my age in there printing—they’re at their desks, writing e-mail, many of them featuring footers like this one:


I’m not kidding: you could determine the age spread of our office simply by analyzing the LAN print queue. The older folk actually print e-mails. (I’m not sure I’ve ever printed an e-mail in my life.) Go up another ten or twenty years, and you’ve got people who print everything, as though the PC is just a really, really fancy typewriter. Continue further up the age scale and you find the people who don’t use computers at all. I’ll never forget the day I showed my first laptop to my grandpa, who was then ninety-six years old. “But it doesn’t do anything!” he cried, picking it up and dropping it on the table. My heart almost stopped, as I feared for my laptop’s hard drive.

Learning curve

As I approach my fortieth birthday this becomes painful to admit, but I’m heading, along with my peers, toward that state of brain ossification that makes any learning difficult. Asking us to unlearn QWERTY, after twenty or more years of using it, is daunting indeed. Naturally, we project this resistance to change onto our children—but we shouldn’t. For them to pick up Dvorak would be—forgive me—child’s play.

Consider this anecdote. The other day, I was chatting online with my brother Bryan, and when I stepped away, my daughter Alexa saw an opportunity to say hi to her uncle. She grasps that because my Windows profile is set to Dvorak, the labels on the keyboard are useless. Not yet able to touch type, she fetched her Dvorak-labeled keyboard, plugged it in, and typed away. She’s seven, and has not yet had a lesson about USB ports, but—being a kid—she evidently figured, “How hard could it be?” I have no concerns about the next generation’s ability to learn Dvorak, no matter how daunting it may seem to us. All we have to do is get out of their way—which means not exposing them to QWERTY.

My autocratic fantasy

I have this game I like to play: If I Were an Autocrat. For example, if I were an autocrat, the following would be illegal: SUVs, bottled water, car alarms, and teaching QWERTY to kids. (I realize that the first three items on this list, if not all four, may have assured the alienation of some of my blog readership. I guess I can live with this. Perhaps in my autocracy you’d be forced to continue reading anyway, and you’d be tested on the material.)

Being a benign autocrat, I would gradually phase in the anti-QWERTY laws. The first phase would require that Dvorak be mentioned, and operating system support guaranteed, to all students. Once the parenting public had been thus exposed to the technology, I would make Dvorak the standard, with a cumbersome opt-out policy whereby a parent would have to apply to a tribunal to explain why QWERTY made sense for his or her child. Eventually it would be a felony to teach QWERTY to kids.

Okay, I’m kidding!

Obviously, that wouldn’t be the most effective way to phase in Dvorak, nor is there much chance of me becoming an autocrat anytime soon. Actually, the best way to jump-start this evolution would be to provide the awareness and basic tools, and let the kids adopt it on their own as a way to simultaneously rebel and out-type their old, lame parents. I’ve even pondered the creation of video games that slyly promote Dvorak. Not lousy games like the Typing Tutor “typing lobster” game I used once, but cool, modern games. You could have one where the player’s weapon requires fast typing of a common word. For example, if you typed the word “the” too slowly, your avatar’s leg would kick back at the knee like when a girl throws a ball; if you typed it in milliseconds your avatar would thrust his hand beneath the rib cage of the opponent and rip out his heart. The kids would eventually figure out that switching to Dvorak is the way to win. (Yes, this is just a joke. Ultra-violent video games are actually on my autocrat-banned list.)

Am I high on drugs?

It might seem highly improbable that this technological problem has a political or legal solution. But things can change fast. I’m still pinching myself over the relatively recent anti-smoking laws. The day I heard they’d be outlawing smoking in San Francisco, I was sure it was a hoax. When the law was passed, and it gradually became apparent that it would actually be enforced, I really felt this was too good to be true. And then other cities across America started following suit, and even Dublin now bans smoking in pubs. Who could have predicted this?

Other laws show how quickly a societal improvement can be adopted. Ever the vanguard, San Francisco has now introduced a compulsory composting law. I’m in awe, frankly, of how seriously this city takes its civic duty. This new law sounds like the kind of thing I might introduce if I had political clout and/or Gavin Newsom's hair.

Is my lifestyle improved by composting? Not directly. All it personally means to me is emptying the kitchen compost bin into the big green waste bin every week, scooping the eerily warm, extraordinarily slimy, chunky, utterly disgusting compost goo off the bottom of the bin with my fingers, fighting the gag reflex and pondering the condensation on the lid of the bin. If the citizens of San Francisco can tolerate a law requiring them to do this, purely out of civic duty, surely we can tolerate a law requiring our kids to be offered Dvorak alongside QWERTY.

Remember the lawyers!

It’s not hard to see how a Dvorak law might take shape. Evidence of a public health issue gives prospective laws some serious teeth. Consider the DEC case: they were forced to pay $6 million in damages because their keyboard was shown to have caused repetitive stress injuries. If I had to guess at why Microsoft Windows supports Dvorak, I’d say it’s protection against lawsuits. After all, why else would they take the trouble, when the number of Dvorak users—though unknown—is likely very small?

Alas, we’re stuck in a chicken-and-egg situation. Before the lawyers get excited about punishing the lack of Dvorak adoption, somebody first needs to establish, in large, well-run scientific tests, the actual efficiency advantage of the Dvorak layout. Once this is established, this keyboard may finally start to gain some traction, and its merit will become widely acknowledged.

National Safety Month

Remember, June is national safety month. So in its honor, why not do something right now to mitigate the risk of a repetitive stress injury? I’m not asking you to switch to Dvorak (though you should). Here are some easy, free things you could do to promote this salutary product:
  • If you’re a parent, consider having your child learn to type on Dvorak
  • Talk to your child’s teacher about offering Dvorak to interested students
  • Read my companion blog post, “The Case Against Margolis & Liebowitz” to gain an appreciation for how a couple of ill-informed economists have helped to cement the ongoing use of QWERTY
  • If you’ve only skimmed this essay, bookmark it for later
If you’ve actually made it to the end of this blog post, congratulations: you have real staying power. In fact, you’re a perfect candidate for actually converting to the Dvorak layout! E-mail me at feedback@albertnet.us if you’d like any tips on how to do this. If not, I’d still like to hear from you. Send an e-mail, post a comment below, or at least take a second to click one of the “reaction” buttons. I’d really like to know if anybody read the whole thing. (The reaction buttons are at the very bottom of this post, past the “useful links.”)

Some useful links

--~--~--~--~--~--~--~---~--
For a complete index of albertnet posts, click here.