+1  A: 

I don't know for Dvorak, but it took me one week to become sufficenty proficient in Colemak layout.

I don't want to start flame wars, but since you are coder you can give it a try since it is better suited for code. Interpunction is in the same places as in qwerty, and some basic shortcuts including letters z x c v q w a are in the same place as in qwerty.

Dev er dev
+2  A: 

Regular typing took me a few weeks. Programming took MUCH longer because braces, parens, etc. are all somewhere else -- and my hands are hard wired to do shift-[ and shift-9. You can always re-map them, though, which is what I ended up doing (same with ctrl-c, ctrl-v).

I would definitely recommend remapping the common keystrokes, otherwise you'll be an absolute useless person if you ever temporarily use another person's computer :D

Matt Rogish
Thanks for your answer. Could you please quantify "Programming took MUCH longer"? Several months? A year?
system PAUSE
Well, the regular typing was fine but the bracing thing annoyed me so much (for a couple of weeks) until I gave up and "cheated" by re-mapping them. So... infinity since I never learned it :D
Matt Rogish
A: 

this is an interesting question, but could you clarify something? are you asking because you've committed to learning dvorak to increase your general typing proficiency/efficiency, or because you want to improve your coding proficiency/efficiency? i dont see how mastering the dvorak keyboard layout makes one a more efficienty/speedier coder, as the layout wasn't designed with that goal in mind.

blackkettle
excellent question
jcollum
Any time you type words (and words are important in programming) Dvorak will be more comfortable, and perhaps avoid some repetitive stress (especially with the left hand.) You won't believe it until you master it yourself, and that's ok.
Jim Carroll
sorry, i wasn't trying to be spiteful, or to indicate that the poster should or should not use the layout. it just seems like the relative key frequencies when i code are substantially different from when im writing an email. the dvorak layout was designed specifically with the latter case in mind. perhaps surprisingly, ive also met quite a few programmers who cant type; and it doesn't seem to make them less efficient at programming; they just are terribly good at mavis beacon.
blackkettle
i wonder if there are any studies out there that look at this subject.
blackkettle
I am asking because I'm curious about the typical time investment needed to become proficient with a new tool. In a similar sense, I'm curious about the typical time investment needed to learn Lisp, or x86 assembly, or OpenGL, or GWT. Whether any given tool is 'better' than what I've got or will make me a 'better coder' is pretty subjective, so I'm asking for raw data. And this isn't exactly a scientific poll, but it's a broader audience, with more chance of useful data than I would get asking around the office. Plus, I think other coders might find the answer useful.
system PAUSE
+3  A: 

I use (one of the many) Spanish Dvorak layout and I got used to it in about a week. Getting my speed back took a little longer; it depends on how long it takes your brain to adapt to a second layout and how much you type with it.

Be aware though, some people have troubles switching back and forth to qwerty and you might be unable to use dvorak in some computers (In my case, I had to create a custom keymap and install it)

XenF
Thanks for your answer. Can you please quantify "Getting my speed back took a little longer"? Was it 2 weeks, 6 months?
system PAUSE
I don't remember. I do remember I had to type a lot of stuff for college at that time, which helped me inmensly.To throw some numbers, in my case I'd say that by 1-2 weeks I stopped "translating" qwerty -> dvorak and started writing dvorak. At this moment I typed slower than with qwerty (I was slower with qwerty too!). Then I started ganing speed. In about a month I was fast with dvorak.And by the way, if you stop typing in qwerty, you'll lose you qwerty speed too, and more importantly, your ability to switch back and forth.
XenF
+1  A: 

Learning to touch-type on Dvorak doesn't take long. Print out a Dvorak layout and stick it to the bottom of your monitor, and just look at that when you're not sure where a key is. You'll be typing in comfort within a few days. Coding won't be comfortable for about another two weeks.

I personally find the Dvorak keyboard layout much more comfortable than QWERTY... but it is important not to forget QWERTY as you learn Dvorak. I learned Dvorak back in college, and once I went to an interview where they tested my typing skills... and they brought out a manual typewriter! Oops! I had brought a floppy disk with drivers for Windows and Mac, but the manual typewriter was something I didn't anticipate. I spent some time on regular QWERTY every so often after that just to make sure I could do both.

One oddity with Dvorak... it puts the n, t, and s keys all under the least coordinated fingers on my right hand. When I'm typing a word that ends with some combination of n, t, and s I'll transpose the letters a bit... but only when I'm typing at full speed.

So I'd encourage everyone to learn Dvorak, especially if you plan on typing for a good chunk of your professional life.

Jim Carroll
+3  A: 

Took me about 12 weeks of programming to get used to it and been using it for years. Have to look at the keyboard to type use Qwerty. The two biggest frustrations are that coding punctuation is awkard to get to as has been noted and that CTRL-V (Paste) and CTRL-W (Close Window) are so close together.

+1  A: 

When I switched over, it took me 3 days to get the layout down, about a week and a half to pick up significant speed at it. It took a couple months before I could type as fast (or better) than the QWERTY layout doing code.

Alex Marshall