DEV Community

Cover image for Why Keyboards Are Not in Alphabetical Order (And Why That’s Actually Brilliant)
Kathirvel S
Kathirvel S

Posted on

Why Keyboards Are Not in Alphabetical Order (And Why That’s Actually Brilliant)

#techtalks #productivity #keyboard #programming

If you look down at your keyboard right now, you’ll see something that feels… wrong.

QWERTYUIOP.

Why isn’t it ABCDEFG?

We alphabetize everything. Contacts. Files. Bookshelves. Even spices in the kitchen (if you’re that kind of person). So why is the one thing we use all day — our keyboard — arranged like someone spilled Scrabble tiles and gave up?

This isn’t random.

It’s one of the most fascinating design stories in tech history.

Let’s rewind.

The Problem: Early Typewriters Kept Jamming

In the 1860s, a newspaper editor named Christopher Latham Sholes invented one of the first practical typewriters.

His early prototypes used — you guessed it — alphabetical order.

And it was a disaster.

Here’s why:

Old mechanical typewriters worked using metal arms (typebars). When you pressed a key, a metal arm swung up and struck an ink ribbon to imprint a letter on paper.

If you typed too fast and hit two nearby letters quickly?

The metal arms collided and jammed.

And guess what letters are often typed together?

Common letter pairs like:

  • T + H
  • E + R
  • I + N

Alphabetical order placed frequently used letters close together — which made jamming happen constantly.

So instead of optimizing for speed…

They optimized to slow people down just enough to prevent jams.

Enter QWERTY

QWERTY Keyboard Layout

Q W E R T Y U I O P
A S D F G H J K L
Z X C V B N M
Enter fullscreen mode Exit fullscreen mode

This is the layout most of the world uses today.

It has ruled desks, laptops, terminals, and IDEs for over 150 years.

This is the layout most of the world uses today.

Sholes rearranged the keys to separate common letter pairs. The result?

The QWERTY layout — named after the first six letters on the top row.

It wasn’t designed to be intuitive.

It was designed to survive mechanical limitations.

Later, Sholes partnered with Remington Arms, which mass-produced typewriters in the 1870s. Once QWERTY shipped commercially, it became the default.

And defaults are powerful.

The Twist: The Problem Disappeared… But QWERTY Stayed

Modern keyboards don’t have metal arms.

They don’t jam.

So why didn’t we switch to alphabetical order once the mechanical issue was gone?

Because by then:

  • Typing schools were teaching QWERTY
  • Businesses standardized on QWERTY
  • Millions of people had muscle memory

Switching would have been expensive and chaotic.

This is called path dependence — when historical decisions lock in future outcomes, even if better options exist.

“But Isn’t There a Better Layout?”

Yes.

In 1936, August Dvorak created the Dvorak keyboard layout. It was designed scientifically:

DVORAK Keyboard Layout

' , . P Y F G C R L
A O E U I D H T N S
; Q J K X B M W V Z
Enter fullscreen mode Exit fullscreen mode

This layout was designed intentionally — scientifically — to improve typing efficiency.

  • Most common letters placed on the home row
  • Reduced finger movement
  • More ergonomic typing

Many studies showed it could improve efficiency.

But it never overtook QWERTY.

Why?

Because the world had already committed.

QWERTY wasn’t the best design.

It was the most adopted.

So Why Not Alphabetical Today?

Here’s the truth:

An alphabetical keyboard would actually be worse for typing.

Why?

Because typing isn’t about remembering letter order.

It’s about:

  • Muscle memory
  • Finger travel distance
  • Letter frequency
  • Hand alternation

Alphabetical order helps beginners find keys.

But it slows down experienced typists.

And once you touch-type, you don’t think “A, B, C…”

Your fingers just move.

The Bigger Lesson for Developers

As developers, this story hits differently.

QWERTY teaches us:

  • Good enough + early adoption beats better + late arrival
  • Technical constraints shape long-term standards
  • Backward compatibility often wins over optimization

Think about:

  • Legacy codebases
  • Old APIs
  • Weird naming conventions
  • Tabs vs spaces

Sometimes we inherit decisions made for constraints that no longer exist.

And we keep them because migration costs more than imperfection.

Final Thought

Your keyboard isn’t alphabetical because history optimized for hardware limitations — not human intuition.

And once the world standardized on it, switching became harder than tolerating it.

So the next time someone asks why keyboards aren’t ABCDEF…

You can tell them:

They were.

It just didn’t work.

Top comments (0)