Visit Website →
← Back to blog

Programmer Dvorak Layout: A Practical Guide for Coders

October 28, 2026
Programmer Dvorak Layout: A Practical Guide for Coders

Programmer Dvorak is standard Dvorak with the same letters but a different top row. Brackets, braces and common code symbols sit unshifted, and digits move to the shifted layer. It suits people who write a lot of source code and want less finger travel. It will not make you dramatically faster, and it has real costs around shortcuts and borrowed computers. This guide covers what changes, what the evidence says, how long the switch takes and how to set it up.

Grounders
kebe.grounders.app
Explore a Keyboard Built for Dvorak
KeBe keyboards use the Matrix-Dvorak layout with low-profile switches and ergonomic designs to reduce finger movement while typing.
Explore KeBe keyboards

TL;DR

  • Programmer Dvorak keeps the Dvorak letter positions and rearranges numbers, punctuation and symbols for code.
  • Expect comfort gains rather than a speed jump: users who have written about it report a calmer feel, not faster typing.
  • One guide estimates 3 to 4 months to get comfortable coming from QWERTY, and 2 to 4 weeks if you already type standard Dvorak.
  • The biggest practical problems are QWERTY-based shortcuts and machines where you cannot install the layout.
  • Learn the letters first, in a trainer, before you touch the symbol row.

Table of Contents

What Programmer Dvorak actually changes

Programmer Dvorak is a sub-layout built on standard Dvorak by Roland Kaufmann. It keeps the Dvorak letter positions and changes punctuation, symbols, numbers and several modifier behaviours to suit source code. If you already know Dvorak letters, nothing about your alphabet changes.

The top row is where the work happens. Standard Dvorak was designed for prose, so its number row stays a number row. Programmer Dvorak instead moves brackets, braces, parentheses and other common symbols to unshifted positions on the top row, and puts the numbers in the shifted positions. The thinking is simple: in C, Java, CSS or Lisp you type far more parentheses and braces than digits, so the symbols get the easy keys.

The digits are not in ascending order either. The number row runs 7-5-3-1-9-0-2-4-6-8, with odd digits on the left and even digits on the right. That sequence is the part most new users complain about, and we come back to it below.

Programmer Dvorak number row with odd and even sides

The layout is aimed at languages with heavy punctuation. Its author says it may suit someone writing C, C#, Java, Pascal, Lisp, CSS or XML, and because the letters are unchanged it also works for English prose. That makes it a reasonable single layout for someone who writes code in the morning and documentation or email in the afternoon.

Programmer Dvorak vs standard Dvorak

The two layouts share their letters, so the comparison is only about everything outside the alphabet.

Standard DvorakProgrammer Dvorak
LettersDvorak arrangementIdentical to Dvorak
Top row, unshiftedDigitsBrackets, braces, parentheses and common symbols
DigitsUnshifted, in orderShifted layer, odd-even sequence
Designed forEnglish proseSource code
Moving from the othern/aRoughly 2 to 4 weeks, by one guide's estimate

The 2 to 4 week figure comes from a layout guide that also gives 3 to 4 months for a QWERTY typist. Treat both as rough: they are estimates, not measurements, and individual results vary widely.

One person who analysed their own repositories found 60% of non-letter characters unshifted on Programmer Dvorak against 55% on standard Dvorak, and added that the analysis is hardly scientific. The gap is modest. If your code is light on symbols, such as a lot of prose-like Python or Markdown, the case for the programmer variant is weaker. If you live in braces and brackets, it is stronger.

Does it make you faster?

Probably not, and anyone promising otherwise is selling something. The evidence is almost entirely personal reports, which is worth keeping in mind.

One developer who switched found Programmer Dvorak more comfortable than QWERTY but no faster, and named shortcuts and switching between computers as the drawbacks. Another account, written three months in, reports less hand movement than QWERTY and more comfort in long sessions. The same author liked having symbols available without Shift but called the shifted, non-ascending number row a serious drawback.

For a longer view, a Microsoft developer wrote about standard Dvorak (not the programmer variant) and described reaching rough QWERTY parity near the end of the third month and a small average-speed gain after six. That is one person's log, not a study.

Long-time users on Stack Overflow echo the same theme: the main benefit is a more sedate, comfortable feel rather than raw speed. So the honest pitch is comfort and less finger travel. If your reason for switching is a sore wrist or tired fingers, that is a fair reason. If it is to ship features faster, your time is better spent elsewhere.

How long the switch really takes

Plan for a dip. For a QWERTY typist, the guide cited above puts adjustment at about 3 to 4 months. In practice that means a few weeks of painful slowness, then a long stretch where you are almost as quick as before, then a stage where it stops feeling strange.

A few things shorten the dip:

  1. Learn the letters on their own. Since Programmer Dvorak's letters are standard Dvorak, practise those first. A free Dvorak typing trainer that introduces one letter at a time keeps you from drowning in 26 new positions on day one.
  2. Add symbols after the letters feel automatic. Writing real code is the best practice for the symbol row, but only once you are no longer hunting for the letter E.
  3. Keep short daily sessions. Fifteen focused minutes beat one frustrating hour.
  4. Choose a low-stakes starting week. Do not switch the Monday before a deadline or an exam.

If you want a structured routine, our guide to a typing trainer keyboard covers how to practise on a layout that fits your hands.

It also helps to keep the rest of your working setup steady while your hands relearn. If you are rebuilding habits anyway, a productivity system for Claude Code is one way to keep your daily workflow predictable during the slow weeks.

The shortcut problem, and the borrowed-computer problem

These two issues come up in nearly every account, so decide how you will handle them before you switch.

Shortcuts. Copy, paste, save and undo are placed for QWERTY: Ctrl+C and Ctrl+V sit under the left hand together. On Dvorak those letters scatter. The macOS fix described by one user is to use Karabiner so you type in Programmer Dvorak while Control, Command or Option combinations behave as QWERTY. Kaufmann's own page also offers a variant with the Ctrl key mapped to QWERTY, and a Windows project on GitHub, glibg10b's Windows layout, is built around the same idea. Whether you keep shortcuts on Dvorak or QWERTY is personal: QWERTY shortcuts preserve muscle memory in editors and terminals, while Dvorak shortcuts keep everything consistent.

Borrowed computers. Programmer Dvorak is not built into every system. It is preinstalled on some Linux distributions but not on Windows or macOS. One student found it unavailable on a university Windows examination computer. If you sit exams, pair-program on other people's machines or do on-site support, check what you can install, and keep your QWERTY from fading entirely. Many people stay bilingual in practice.

The shortcut problem, and the borrowed-computer problem — overview diagram

Installing Programmer Dvorak on Windows, macOS and Linux

The setup differs by system, and none of it is difficult.

After installing, check four things: your terminal emulator, your editor's shortcuts, your game controls (many games bind WASD to physical keys, which is fine on a layout where those keys differ only if the game reads key positions), and any remote desktop or virtual machine, which may apply its own layout on top of yours.

The layout is software, so it works on any keyboard. Physical shape still matters for comfort, though. If you are weighing a split or ortholinear board, read ergonomic keyboard vs regular first.

Which layout suits which programmer

There is no universally best keyboard layout for programming. The right pick depends on what you type and where.

  • Programmer Dvorak fits you if you write symbol-heavy languages most of the day, work mainly on your own machines and are switching for comfort.
  • Standard Dvorak fits you if your work is half prose, half code, or you want a smaller first step. You can move to the programmer variant later; the guide above suggests that second step is quick.
  • QWERTY fits you if you constantly use other people's computers, rely on shortcut-heavy tools, or have no comfort problem to solve.

One question from a forum thread compared Dvorak with Colemak-style alternatives for coding, gaming and essays. Those are different trade-offs again, and the same rule applies: pick one, give it a few months, and judge it by how your hands feel.

Why most people stay on QWERTY

The reasons are practical rather than mysterious. QWERTY is what every shared computer, school lab and new laptop assumes. Switching costs weeks of reduced output, shortcuts are placed for QWERTY, and the speed payoff is unproven for most typists. When the gain is mainly comfort, many people never feel enough pain to justify the dip. That is a reasonable decision, not a failure of imagination.

Our perspective: the layout is half the picture

We build keyboards around a Matrix-Dvorak layout: a straight-column key grid with hand-centred letter placement, meant to reduce finger movement and typing fatigue. So we like what Dvorak-family layouts are trying to do. But after looking at what people report, our view is this.

First, comfort comes from the whole system. A layout that shortens finger travel helps most when the keys sit in straight columns that match how fingers actually move, rather than a staggered grid inherited from typewriters. That is why our boards are ortholinear, and why we think the physical and the logical layout should be chosen together.

Second, be honest about the learning curve. The number row on Programmer Dvorak is the sticking point for many, and nobody should expect a speed boost. We would rather you switch for comfort, with eyes open, than for a promise.

Third, make practice easy. Typo correction and a built-in trainer exist in our design because the first weeks are the hardest, and mistakes in those weeks are what make people quit.

— Joshua

Try a Dvorak-based keyboard built for it

If you are ready to try a layout that cuts finger movement, KeBe makes ergonomic ortholinear keyboards with a Matrix-Dvorak layout, assembled by hand in Canada. Options include the mechanical KeBe v2 with low-profile switches, hot-swappable keys and per-key RGB lighting, and the slim KeBe Lite, which is planned. You can see the range and pre-order or join a waitlist in our Canadian store.

If you are still choosing features, our guides on hot-swappable keyboards and mechanical vs membrane explain what matters before you buy.

FAQ

What is the difference between Dvorak and Programmer Dvorak?

The letters are identical. Standard Dvorak is built for prose and keeps digits on the top row. Programmer Dvorak moves brackets, braces and common symbols to unshifted top-row positions and puts numbers on the shifted layer, in an odd-even order.

What is the best keyboard layout for programming?

No layout is proven best. Programmer Dvorak suits symbol-heavy code and comfort-focused typists, standard Dvorak suits mixed prose and code, and QWERTY suits anyone who moves between many machines. Choose by the comfort you want and the shortcuts you rely on, not by speed claims.

How do I enable Programmer Dvorak on Windows or macOS?

Neither system includes it by default, so download it from the layout author's page, which offers installers and a macOS package. Then add it as an input source and test it in your editor and terminal. On Linux, use the dvp layout in XKB.

Why don't most people use Dvorak?

QWERTY is the default on nearly every computer, switching means weeks of slower typing, and shortcuts are laid out for QWERTY. Reports from users suggest the gain is mainly comfort, not speed, which is a weak reason to switch for many people.

Sources