Typing for Programmers: Symbols, Shortcuts and Code Practice
10 minute read
A developer who types 80 WPM on English prose can easily drop to half that speed when typing real code. That isn't a sign of poor skill — code is a genuinely different kind of text. It is dense with symbols, brackets, operators, mixed capitalisation and precise indentation. This guide explains what makes code typing hard and how to practise it deliberately.
Why code is harder to type than prose
- Symbols everywhere. Characters like
{ } [ ] ( ) ; : = > < | & _ $ #appear constantly and mostly live on the top row or require Shift. - Pinky overload. On a standard QWERTY layout, many programming symbols are typed with the right little finger — often the weakest finger.
- Unpredictable words. Variable and function names like
getUserByIdormax_retriesdon't follow normal spelling patterns your fingers already know. - Case changes. camelCase, PascalCase, snake_case and CONSTANT_CASE require constant Shift use and underscore reaches.
- Exact precision. In prose, a typo is ugly. In code, a missing semicolon or bracket can break the whole program.
Master the symbol keys
Most developers never formally learn where symbols are — they just hunt for them. That's where a big chunk of lost speed hides. The standard touch-typing assignments are:
Right pinky
- = [ ] \ ; ' / and their shifted versions _ + { } | : " ?
Number row
Shifted numbers give ! @ # $ % ^ & * ( ). Use the same finger that types the number underneath.
Shift key rule
Use the Shift key on the opposite hand from the key you're pressing. For { (right pinky), hold left Shift.
Brackets as pairs
Practise typing (), [], {} and "" as single two-key movements.
How to practise code typing effectively
Use real code, not random symbols
Random symbol drills help a little, but real code teaches the patterns that actually appear: ) {, =>, !==, ->, ::, $this->. The Code track in our typing test includes real snippets in Python, JavaScript, TypeScript, PHP, Java, Go, C, C++, SQL, Bash, CSS, HTML and React.
Let indentation take care of itself
Real editors auto-indent, so manually typing leading spaces isn't a skill worth drilling. In our Code track, indentation fills in automatically after you press Enter, so you practise what matters — the code itself.
Practise the languages you actually use
Each language has its own symbol habits. PHP is full of $ and ->; JavaScript uses => and backticks; Python relies on colons and underscores; C uses *, & and ->. Focus your practice where you spend your working hours.
Measure accuracy, not just speed
In code, accuracy matters even more than in prose. A fast typist who constantly backspaces over mistyped brackets isn't really fast. Watch your error count and heatmap as closely as your WPM.
Editor shortcuts that save the most time
Raw typing speed is only part of developer productivity. Knowing your editor often saves more time than typing faster. These shortcuts are for VS Code on Windows/Linux (on Mac, use Cmd in place of Ctrl); many other editors have similar ones.
- Ctrl+P — quickly open any file by name
- Ctrl+Shift+P — command palette for almost any action
- Ctrl+D — select the next occurrence of the current word (multi-cursor editing)
- Alt+↑ / ↓ — move the current line up or down
- Shift+Alt+↓ — duplicate the current line
- Ctrl+/ — toggle comment on the selected lines
- Ctrl+Shift+K — delete the current line
- F2 — rename a symbol everywhere it's used
- Ctrl+← / → — jump by whole words instead of single characters
Learn two or three at a time and force yourself to use them for a week. Trying to memorise all of them at once rarely sticks.
Keyboard layout and hardware for developers
Some developers switch to alternative layouts like Dvorak or Colemak, or to programmable keyboards that move symbols to easier positions. These can help some people, but they come with a real cost: relearning time and awkwardness on other people's computers. For most developers, mastering standard QWERTY symbol positions delivers most of the benefit with none of the switching pain.
Frequently asked questions
Does typing speed really matter for programmers?
Programmers spend much more time thinking and reading than typing, so typing speed isn't the main skill. But fluent typing removes friction — you stop losing your train of thought while hunting for a bracket. Accuracy with symbols matters most.
What's a good code typing speed?
Because code is denser than prose, expect your code WPM to be noticeably lower than your English WPM. Compare yourself against your own previous code results rather than against prose benchmarks.