Touch typing for programmers: brackets, symbols and real code
Programmers spend most of their time thinking, not typing. But when the typing is slow or error-prone, it breaks the thinking: you look down for a curly brace, mistype an operator, lose the thread. Fast, accurate code typing keeps you in flow. It also differs from prose typing in ways that ordinary typing tests don’t train.
How code is different
- Symbols everywhere.
{ } ( ) [ ] < > = ; : " ' _ - + * / \ | & ! ? # $ %appear constantly. In English prose most of these almost never show up. - Shift all the time. Many symbols need Shift, and camelCase names need it mid-word.
- Exact text matters. One wrong character can break a program, so accuracy matters even more than speed.
- Structure. Line breaks and indentation carry meaning, especially in Python.
Learn where the symbols live
Most people who touch type letters still hunt for symbols. On a standard US/UK-style keyboard:
| Keys | Finger |
|---|---|
( ) (Shift + 9, 0) |
right ring, right little |
[ ] { } |
right little finger, reaching up and right |
- _ = + |
right little finger, top row |
; : ' " |
right little finger, home row |
/ ? and \ | |
right little finger, bottom row / above Enter |
< > (Shift + , .) |
right middle, right ring |
! @ # $ % (Shift + 1–5) |
left hand, little to index |
^ & * (Shift + 6–8) |
right index and middle |
Notice how much work lands on the right little finger. Practise those reaches slowly until they’re reliable; that’s where most programmers lose time.
Remember the opposite-Shift rule: for symbols on the right side, hold left Shift.
Practise with real code
Drills of random symbols help a little, but real code is better: it has the patterns you’ll actually type, like
) {, =>, !==, [i], ");, :=.
TypeHub’s Code mode (press Esc then o) gives you short, readable snippets in 12 languages: JavaScript,
TypeScript, Python, Java, C++, C, Go, Rust, HTML, CSS, SQL and Bash. Switch language with Esc then d, or the
Language row.
- Line breaks are real. At the end of a line press
Enter(Space also works). - Indentation is shown, not typed, like an editor that indents for you, so you practise the code itself, not pressing the space bar four times.
- A monospace font keeps everything lined up.
- Your results show the same speed, accuracy and consistency stats as any other test, and Weak keys mode will start picking up the symbols you miss.
A 15-minute routine for developers
- 5 minutes, your main language. Accuracy first: aim for 97%+.
- 5 minutes, a language you use less. Different languages stress different keys: Rust and C++ love
::and<>, SQL is mostly words and commas, Bash has$and|. - 5 minutes of plain prose. Commit messages, comments, documentation and chat are prose, and they deserve speed too.
Habits that make you faster at a real keyboard
- Learn your editor’s shortcuts for the things you do most (duplicate line, move line, multi-cursor). They save more time than raw speed.
- Let autocomplete help, but know the keys anyway. You’ll still type a lot by hand: in terminals, reviews and chat.
- Don’t look down for brackets. If you’re unsure, check the on-screen keyboard (Preferences, or
Escthenk) instead. - Keep your wrists relaxed. Coding sessions are long; see Typing without wrist strain.
What about AI coding assistants?
They change what you type more than whether you type. You’ll write fewer boilerplate lines and more prompts, reviews and explanations. That’s why TypeHub also has an AI prompt mode; read Typing AI prompts faster.