Alternate Keyboard

I switched to an alternate keyboard layout a few years ago and never looked back. It took about three months to feel natural. For me, the payoff was less finger travel, less perceived strain, and better accuracy. Those are personal observations, not a controlled ergonomics study.

Most of us still type on QWERTY, a layout that emerged with nineteenth-century typewriters and became a de facto standard. The familiar story that QWERTY was simply designed to slow typists down is too neat: historians still debate how much mechanical constraints, telegraph workflows, and early operator feedback shaped the layout. The important point for me is simpler: QWERTY’s persistence does not make it the only reasonable layout for a modern keyboard.

I tried Dvorak, but settled on Colemak because it keeps more keys in familiar positions while moving many common letters toward the home row. That reduced the amount I had to relearn while still changing the feel of everyday typing.

Training the New Layout

The most useful part of the transition was deliberate typing practice. GNU Typist includes structured drills, and the feedback loop is immediate enough to make relearning feel measurable rather than vague.

Typical package-manager installs include:

  • brew install gnu-typist
  • pacman -S gtypist on Arch Linux

Short daily practice worked better for me than switching back and forth whenever I became frustrated. After a few weeks, the new layout stopped feeling foreign; after a few months, it became the default movement pattern.

Moonlander, but Not Mine

I use a Moonlander and like one property in particular: the layout can live on the keyboard itself.

That means the operating system can remain configured as QWERTY while the keyboard presents Colemak anywhere it is plugged in. For someone who moves between machines, keeping the mapping in firmware avoids a surprising amount of host-specific configuration.

The broader lesson is not that one keyboard is required. A programmable split keyboard makes alternate layouts easier because it can provide:

  • firmware-level remapping
  • layers for navigation and symbols
  • visual cues while learning
  • independent positioning of each half
  • thumb keys that move work away from the little fingers

Those features can make a layout transition easier to sustain, but comfort is personal and depends on posture, desk setup, switches, workload, and existing injuries as much as the letter arrangement itself.

Conclusion

Colemak works better for me than QWERTY. Most of my common typing motion stays near the home row, and combining that with Vim and other keyboard-driven workflows makes the computer feel more direct.

The larger lesson was that defaults are not obligations. A keyboard layout is an interface, and interfaces can be changed when their trade-offs no longer fit the person using them.

Passwords can also become confusing during the transition, which is another good reason to rely on a password manager rather than muscle memory.

References