Do Developers Still Need to Type Fast in the Age of AI?

1. How Much Code Do Developers Actually Type Now?

Less than they did in 2021, and more than the marketing suggests. AI assistants are excellent at the code that was always cheap to type: boilerplate, scaffolding, standard library calls, test skeletons, the fifth CRUD endpoint that looks like the other four. That work has genuinely shifted to autocomplete and agents, and about three in four developers now use or plan to use these tools according to the Stack Overflow Developer Survey.

What did not shift is everything around the generated code. You still type the prompt that describes the problem. You still type the follow-up that corrects the model's first attempt. You still type the edits that adapt generated code to your codebase's conventions, the test cases the model did not think of, the commit message, the code review comments, and the Slack thread explaining the decision. A working day that used to be 80% code and 20% prose has drifted toward the reverse - but nearly all of it is still typed.

In other words: AI reduced the volume of code typing and increased the volume of prose typing. If your prose speed is weak, the AI era made your typing bottleneck worse, not better.

2. What Do the Studies Actually Show?

The two most-cited controlled studies point in opposite directions, and both are probably right - about different situations.

The reconciliation is straightforward. AI shines on self-contained tasks where the model's training data has seen a thousand versions of the answer. It struggles when the task depends on deep, unwritten context - exactly the work senior developers do in mature codebases. The METR result's most important detail is the perception gap: developers felt 20% faster while measuring 19% slower. Time spent prompting, reading, and correcting feels productive even when it is not.

For typing, the implication cuts both ways. When AI genuinely accelerates you, the remaining human work - prompts and review edits - becomes the bottleneck. When it slows you down, fast correction cycles are what claw the time back. Neither case makes keyboard fluency less valuable.

3. From Writing Code to Steering It

The defining loop of AI-assisted development is: describe, generate, read, correct, repeat. Three of those four steps are typing. A precise two-sentence prompt beats a vague one-liner, a specific correction beats "that's not quite right" - and precision costs characters.

There is also a latency argument. An agent that answers in seconds makes you the slow link in the chain. If composing a correction takes you ninety seconds of hunt-and-peck, you will send fewer, lazier corrections - and accept worse code. Iteration count is a quality lever, and typing speed sets your iteration budget.

4. The Typing That Remains Is the Hardest Typing

Here is the part almost nobody talks about. We measured the character composition of all 1,350 code snippets in our practice library: depending on language, 18.3% (Java) to 29.2% (Rust) of non-space characters are symbols - brackets, operators, quotes, sigils - and code is typed at only 55-70% of the same person's prose speed largely because of them.

AI autocomplete is best at the flowing, predictable, low-symbol middle of a file. What it leaves for your hands is the opposite: the surgical edit inside a nested generic, the corrected lifetime annotation, the off-by-one fix in a slice expression, the closing-bracket run after restructuring a block. Hand-editing generated code concentrates your keystrokes in precisely the characters that were always the slowest and most error-prone to type - the special characters.

So the AI era does not just preserve the case for typing practice - it sharpens it. General typing tutors drill prose. What developers increasingly need is fluency in exactly the symbol clusters that survive automation, which is what language-specific code practice trains.

5. Why Speed Still Compounds

Typing speed was never really about words per minute. It is about whether the keyboard is transparent. When typing is automatic, your working memory stays on the problem; when it is effortful, every sentence you compose to an AI - or line you fix in its output - taxes the same cognitive budget you need for the actual engineering. That argument predates AI and survives it untouched.

• •

  More interfaces, same keyboard. Editor, AI chat, terminal, PR review, docs, Slack - the modern workflow multiplied the surfaces you type into.

• •

  Review is the new bottleneck. Reading generated code and annotating what is wrong with it is now a core skill, and annotation is typing.

• •

  Flow is fragile. The developer who can capture a thought in five seconds keeps it; the one who needs thirty often loses the thread - to a notification, or to the AI's next suggestion.

6. What About Voice?

Voice input is the one genuine challenger, and it is improving fast. For prose-shaped work - prompts, commit messages, comments, chat - modern dictation is already competitive with typing for many people, and voice-first tools are emerging (including Crodo, a macOS voice assistant we build - full disclosure).

But voice and symbols do not mix. Try dictating a Rust turbofish or a nested ternary. For the symbol-dense editing that survives automation, the keyboard remains an order of magnitude more precise, and it works in an open-plan office. The realistic 2026 setup is hybrid: voice for English, keys for code - which means the keyboard skills worth training are shifting toward exactly the hard, symbolic residue described above.

7. What Speed Should You Aim For?

The benchmarks have not moved: 50-70 WPM on plain prose, 30-45 WPM on real code is a comfortable professional range - the full reasoning is in our typing speed benchmarks guide. What has moved is the emphasis: prose speed matters more than it did, because prompts and reviews are prose; and accuracy on symbols matters more than raw code WPM, because your code keystrokes are increasingly corrective edits where a typo costs a whole extra AI round-trip.

If you want a baseline, the 60-second coding typing test gives you WPM and accuracy on real code in nine languages, free and without signup.

8. Frequently Asked Questions