Visit Website →
← Back to blog

Dvorak for Programming: Is It Worth Switching?

October 29, 2026
Dvorak for Programming: Is It Worth Switching?

Dvorak can be a good fit for programming, but only if you pick the right version and go in with realistic expectations. Standard Dvorak speeds up English prose more than code, because code is full of brackets, braces and operators. That is why Programmer Dvorak exists: it keeps the Dvorak letters and rearranges the number and symbol rows around programming syntax. The catch is a few months of slower work, friction with shortcuts, and the fact that the speed gain is smaller than most enthusiasts claim.

This guide covers what changes, what the evidence actually shows, what it costs you in daily use, how to install it on Windows, macOS and Linux, and when a different fix is smarter.

Grounders
Make Your Keyboard Fit Your Workflow
KeBe keyboards use the Matrix-Dvorak layout, ergonomic designs, and low-profile switches for typists seeking a more comfortable coding setup.
Explore KeBe keyboards

TL;DR

  • Programmer Dvorak keeps Dvorak's letter layout but puts symbols on the unshifted top row and digits on the Shift layer, which suits C-style code better than standard Dvorak.
  • Research on Dvorak's speed advantage is mixed and often weak, so switch for comfort and curiosity, not for a guaranteed productivity jump.
  • Expect weeks to reach workable speed and several months to a year to pass 50 WPM, with shortcuts and other people's computers as the ongoing friction.
  • Symbol entry, not the letter layout, is the real bottleneck in code, so your keyboard hardware and layers matter as much as the layout.
  • Practise first on a free trainer and install the layout at the OS level before you spend anything.

Table of Contents

What Dvorak and Programmer Dvorak actually are

The Dvorak Simplified Keyboard was patented in 1936 by August Dvorak and William Dealey. It puts the most common English letters on the home row, with the goal of cutting finger travel and improving comfort compared with QWERTY. All the vowels sit under your left hand, and the most frequent consonants under your right.

That design was tuned for English text. Source code looks different: parentheses, semicolons, curly braces, underscores, equals signs and quotes appear constantly, and on a standard Dvorak board many of them sit in awkward spots.

Programmer Dvorak, created by Roland Kaufmann, answers that. It shares the same letter layout but requires Shift to reach digits, which frees the top row for symbols such as brackets, braces and common operators. The digits themselves sit in the Shift layer in the order 7-5-3-1-9-0-2-4-6-8.

In practice that means:

  • Letters: identical to standard Dvorak, so everything you learn transfers.
  • Top row, unshifted: symbols you use in code, such as parentheses, brackets, braces and the asterisk.
  • Top row, shifted: digits, in the unusual order above.

One analysis by Michał Nazarewicz suggests the arrangement reduces how often you need Shift by putting frequent programming punctuation in unshifted positions. The same analysis cautions that counting characters in source files does not always reflect real key presses, since editors insert closing brackets automatically and you paste a lot of text.

Is Dvorak good for programming? What the evidence says

The honest answer is that nobody has produced solid proof either way.

On the pro side, Ober's review of 47 publications found that most studies favoured Dvorak, but many had methodological weaknesses. A study of eight typists on high-frequency digraphs found Dvorak 4.0% faster than QWERTY, a modest margin from a small sample.

On the sceptical side, economists Liebowitz and Margolis argue that claims of Dvorak's superiority rest on scant, suspect evidence and that QWERTY's continued use is efficient. Wikipedia's summary is similar: the case for reduced finger motion and fewer repetitive strain injuries remains debated.

Then there is the programmer's view. Several developers who made the switch report that typing source code did not get much faster, because code is mostly symbols. One Canadian developer, Jesse McDowell, wrote in 2024 that code was not much quicker on Dvorak and that he ended up relearning QWERTY for the devices and computers he could not control.

So a fair summary:

  1. Speed: a small gain at best, hard to measure, and wiped out for months by retraining.
  2. Comfort: many people find less finger travel pleasant, though the injury-prevention claim is not settled.
  3. Programming fit: Programmer Dvorak is a clear improvement over plain Dvorak for C, Java and similar languages. One commentator notes it is much worse for number-heavy work such as spreadsheets or accounting, because every digit needs Shift.

If your day is mostly code and prose, the trade is reasonable. If you also key in numbers all day, think twice.

How symbols are arranged compared with QWERTY and standard Dvorak

On QWERTY, the top row gives you digits unshifted and symbols shifted. Brackets and braces live far to the right, on the edge of the board, and parentheses require Shift on the 9 and 0 keys. Standard Dvorak keeps that same number-row logic, so your symbols stay shifted and spread out.

Programmer Dvorak flips the top row. The symbols that code uses most get the unshifted spots, and digits move behind Shift. The trade is simple: you type (, [, { and * with a single press, and pay Shift when you need a number.

Top-row symbol and digit layout comparison

This suits languages where punctuation outweighs numerals. It suits them less when you write many numeric literals, work in spreadsheets, or use shortcuts that rely on number keys, which brings us to the costs.

The real drawbacks for coding and daily use

The layout is rarely the problem. The surrounding world is.

Shortcuts

Cut, copy and paste are the classic casualty. In QWERTY, X, C and V sit together under your left hand, which lets your right hand stay on the mouse. In Dvorak they scatter, so that one-handed habit stops working. Ctrl-C and Ctrl-V are no longer adjacent, though the letters remain memorable as command names.

Programmer Dvorak adds a second wrinkle. Because numbers need Shift, shortcuts that include a digit, such as Command-Shift-4 for screenshots on a Mac, become unusable or confusing. Many people fix this with software. On macOS, a tool such as Karabiner can restore QWERTY positions when you hold a modifier, which keeps shortcuts where your hands expect them.

Other people's machines and devices

If you pair-program, help a colleague, or sit at a shared workstation, you will meet QWERTY. The same developer notes QWERTY is also on phones, TVs, consoles and printers. Ars Technica's reader survey described the central trade-off as ecosystem friction: many people who tried to switch quit, often because of QWERTY switching and programming difficulty.

Another pain point is letting someone else use your machine. They face a layout they cannot type on, so a quick toggle or a spare profile helps.

Games

If you also game, check your titles first. The Dvorak Gamer Index reports that games often assume QWERTY-style controls: many allow remapping, but some do not remap every control or accept punctuation keys. Switching layouts can also require restarting a game. For games with no remapping, QWERTY is the only option, and people who have lost their QWERTY habit can struggle with chat, searches and in-game names.

The transition dip

You will be slower for a while. One developer's write-up on moving to Dvorak puts it plainly: you accept being slower temporarily in the hope of working faster later. During his transition, another writer found that coding was slower because programming leans on symbols, which is exactly the problem Programmer Dvorak tries to ease.

How long it takes to learn

Ars Technica reported that readers reached workable Dvorak speeds in roughly a week to a few months, while 50 words per minute or more commonly took several months to a year. Keyboard specialist Pascal Getreuer says learning an alternative layout takes at least a couple of months of daily practice.

A realistic plan looks like this:

  1. Weeks 1 to 2: drill letters on a trainer for 15 to 30 minutes a day. Keep your work on QWERTY.
  2. Weeks 3 to 6: use Dvorak for chat, email and personal projects. Keep an on-screen layout diagram nearby, which Ars Technica suggests as an aid.
  3. Months 2 to 3: switch your daily coding to the new layout when your prose speed is comfortable. Practitioners advise starting at home rather than jumping in during a deadline-heavy week.
  4. Month 3 onward: fix shortcuts with remapping, and decide how you will handle QWERTY machines.

If you want a no-cost place to start, our free Dvorak typing trainer teaches one letter at a time, and our guide to a typing trainer keyboard explains how to practise on a layout that fits.

How to install Dvorak or Programmer Dvorak

Try it in software before you buy anything.

Windows

In Windows 11, add United States-Dvorak under Settings, Time and Language, Language and Region. One user in that thread reports Windows sometimes switches back to QWERTY, so check the active layout in the taskbar if letters suddenly look wrong. For Programmer Dvorak, Kaufmann says drivers are provided for Windows, Linux and macOS, so download the Windows installer from his page.

macOS

Programmer Dvorak ships as a keyboard layout file you add in System Settings under keyboard input sources. Walkthroughs show how to add it to the list of available layouts and use it as your only layout. If your shortcuts feel wrong, look at the Karabiner approach mentioned above.

Linux

The layout is already there. ArchWiki lists Programmer Dvorak as dvp for Xorg and dvorak-programmer for the Linux console. Set it through your desktop's keyboard settings or with setxkbmap.

Canadian note: if you use the Canadian Multilingual layout for French accents, keep it as a second input source so you can toggle for accented letters.

Perspective: why we think the layout is only half of it

We build keyboards around a Dvorak-based Matrix layout, so you might expect us to tell you to switch and never look back. We will not. The evidence for a big speed win is thin, and a layout swap on its own leaves your wrists, your shortcuts and your symbol problem exactly where they were.

Perspective: why we think the layout is only half of it — overview diagram

What we have seen matters more is the combination. Letters under the right fingers help. A straight-column grid that reduces sideways reaching helps. And the thing programmers actually fight is symbols: Pascal Getreuer argues that the main bottleneck in programming is symbol entry rather than the alpha layout, and that a custom symbol layer on a programmable board can beat a fixed layout like Programmer Dvorak. We agree with the spirit of that. It is why we care about hot-swappable switches, per-key lighting that helps you learn a new map, and a layout you can make your own.

Our advice: treat Dvorak as a comfort project, not a speed hack. Practise for free first. Choose Programmer Dvorak if you write C-family code and few numbers. Keep a QWERTY fallback for the world outside your desk. If after two months your hands feel better, then think about hardware that matches the way you now type.

— Joshua

Hardware that fits a Dvorak workflow

Once you commit to a layout, the board matters. A few things help a switcher in particular:

Not ready to switch? Other ways to ease symbol strain

Switching layouts is not the only fix, and for some people it is the wrong one.

  • A symbol layer. Remap a held key to give you brackets and operators under your home row, whatever the base layout.
  • Editor features. Auto-closing brackets and snippets cut keystrokes without changing a single key, though they also mean raw character counts overstate your typing.
  • Better posture and a better board. If your complaint is wrist or finger fatigue, an ergonomic board may help more than a new letter map.
  • Stay on QWERTY with a shared setup. If you pair-program daily or hop between machines, the friction cost may outweigh any gain. The Microsoft developer who wrote about Dvorak argued that faster typing is not the same as better programming, and that practice and the ability to work on QWERTY systems matter more.

Try a Dvorak-ready keyboard from KeBe

KeBe keyboards are built around the Matrix-Dvorak layout with a straight-column key grid, hand-centred letter placement, hot-swappable keys, per-key RGB lighting, integrated USB-C ports and a hub, autocorrect and a dual-spacebar design. They are assembled by hand in Canada, and you can pre-order or join the waitlist for upcoming models.

Grounders

If you want to see what suits your hands, start with the free typing trainer, then browse the KeBe store for current models and availability.

FAQ

Is Dvorak good for programming?

It can be, mostly for comfort. Standard Dvorak helps with letters, but code is symbol-heavy, so many programmers prefer Programmer Dvorak. Studies on speed are mixed, and several developers report little gain once they were fluent.

What is the difference between Dvorak and Programmer Dvorak?

They share the same letter layout. Programmer Dvorak puts programming symbols such as brackets and braces on the unshifted top row and moves digits to the Shift layer. That helps with C-style code and hurts with number-heavy work.

How long does it take to learn Dvorak for coding?

Plan on a week to a few months for workable speed and several months to a year to pass 50 WPM, based on Ars Technica's reader reports. Coding usually comes after prose, because symbols and shortcuts add a second learning curve.

Will Dvorak break my keyboard shortcuts?

Some of them. Copy and paste lose their neat left-hand cluster, and with Programmer Dvorak any shortcut that uses a number key needs Shift. Remapping tools such as Karabiner on macOS can restore QWERTY positions while a modifier is held.

Can I still use QWERTY after learning Dvorak?

Yes, but it takes upkeep. Many switchers find they must relearn QWERTY for shared computers and devices, and keeping both layouts sharp is demanding. Keep a quick layout toggle and practise both occasionally.

Sources