Typing for Programmers: Symbols, Brackets and Real Coding Speed
Why coding speed differs from normal typing, which keys slow programmers down, and how to practise code typing in JavaScript, Python and more.
By the TypePlay team · · 2 min read
Programmers type a lot, but not the same way writers do. Code has fewer long words and far more symbols: brackets, braces, operators and punctuation. A fast prose typist can still crawl through a line of code if those keys are not automatic.
The keys that slow programmers down
- Brackets and braces: ( ) [ ] { } all sit at the right edge and most need Shift.
- Operators: = + - * / < > and combinations like => and !==.
- Underscores and hyphens in names, such as read_file or justify-content.
- Quotes, semicolons and colons at the end of lines.
- Numbers, especially mixed with symbols.
Measure code, not prose
A normal word test will not show these weak spots. Test with real code instead. TypePlay has typing tests for JavaScript, Python, Java, C, HTML, CSS and SQL, each using short, real snippets.
Technique tips
- Use the opposite Shift key from the symbol: right Shift for symbols on the left, and the other way round.
- Keep your right little finger near its home key; most brackets are its job.
- Practise common pairs as one movement: (), {}, [], =>, ();
- Type closing brackets yourself during practice, even if your editor usually adds them.
A short daily routine
- Five minutes of normal word practice to warm up.
- Five minutes on the code test for your main language.
- Five minutes on a second language to keep symbol skills broad.
Track your code WPM separately from your word WPM. A good target is code speed at around two-thirds of your prose speed with high accuracy, since one wrong character can break a program.
Try it on TypePlay
- JavaScript typing test →Arrow functions, braces and callbacks.
- Python typing test →Colons, brackets and snake_case names.
- Code typing test →Mixed snippets for any programmer.
Free, in your browser, no account needed.
Questions and answers
Does typing speed matter for programmers?
Less than thinking, but it still matters. Typing without looking and without stopping for symbols keeps you focused on the problem instead of the keyboard.
Why is my coding WPM lower than my normal WPM?
Code is full of symbols that need Shift or long reaches, such as { } ( ) and _. Because WPM counts characters, those slower keys lower the score. Compare code results only with other code results.