Why typing code is a different skill
A prose test cycles through the same 26 letters and a space. A code test drags you through shift-modified symbols — braces, brackets, angle brackets, pipes, backticks — and every one of them is a two-key reach that breaks your rhythm.
Most developers plateau at a code speed well below their prose speed, and the cause is almost never vocabulary. It is the pinky reaching for symbols, and the habit of pausing after every line to think. This test separates those two costs: the text never changes meaning, so any hesitation you see is a motor problem, not a thinking problem.
What this test measures
- Net WPM and raw WPM, calculated the same way as the prose test: five characters per word.
- Accuracy per character — a misplaced brace counts exactly as much as a misplaced letter.
- Indentation is skipped automatically, because nobody wants to be graded on pressing space four times.
- Best runs are stored locally per language, so you can see whether SQL is genuinely slower for you than JavaScript.
A realistic expectation
If you type prose at 90 WPM, expect your first code run to land somewhere between 40 and 60 WPM. That gap is normal and it is not a sign that you type badly. Developers who practise symbol reaches deliberately tend to close most of it within a few weeks.
How to practise deliberately
- Stay on one language for a week. Switching every run hides your progress.
- Type at 90% of your maximum. Sprinting produces errors that teach your fingers the wrong pattern.
- Find your slowest symbol and repeat it. For most people it is the underscore, the bracket, or the backtick.
- Keep your hands on the home row even when you miss. Looking down resets the motor memory you are trying to build.
Type in your language
Each language breaks your rhythm in a different place. Pick the one you write all day and the score becomes something you can actually track.