Why has my typing speed stopped improving?

Common letters are already automatic, so general practice adds nothing. The remaining time is being lost on symbols and the number row, which ordinary text barely exercises.

What is a good intermediate typing speed for a developer?

Around 60 to 70 WPM on code with accuracy above 97 percent is comfortably sufficient for professional work. Expect your code speed to sit well below your prose speed.

Should I move to advanced snippets?

Only once accuracy is consistently above 97 percent here. Advanced material is symbol-saturated, and practising it at low accuracy rehearses mistakes rather than technique.

Intermediate typing test

Real functions with branching, loops and the usual punctuation load.

0 wpm100% acc0sstart typing…

function debounce(fn, delay) { let timer; return function (...args) { clearTimeout(timer); timer = setTimeout(() => fn.apply(this, args), delay); }; }

What to watch

{ }Shifted brackets opening and closing blocks.
( )Every call, condition and parameter list.
=>Two-character operators start appearing in volume.
0-9The number row, where accuracy usually collapses first.

This is where the plateau happens

Most developers reach a comfortable intermediate speed and stay there for years. The reason is that ordinary practice stops producing gains once the common letters are automatic — and the remaining time is being lost somewhere else entirely.

That somewhere is almost always symbols and the number row. General typing practice barely touches them, so they never improve, and they set the ceiling for everything else.

Brackets come in pairs, so practise them in pairs

The difficulty with an opening bracket is rarely the opening character. It is returning to the matching close after your hand has moved through a line of content, which is a different movement each time depending on what came between.

Because of that, drilling brackets in isolation teaches very little. Real function bodies, where the closing bracket arrives after genuine content, are the material that transfers.

Check your consistency, not just your speed

At this level WPM stops being the useful number. Two people at the same speed can be typing completely differently: one steady, one sprinting through familiar words and stalling on hard ones.

Consistency exposes that. If yours is low while accuracy is fine, your speed is coming from bursts, and the pauses between them are where your remaining time sits. Finding the characters that cause those pauses is worth more than any amount of general practice.

Use the heatmap to choose your next drill

After a few sessions the heatmap will name your two or three worst keys by total errors. For most developers at this level they are number-row characters and the underscore, not the exotic symbols people expect.

Fix two at a time, re-check, then move to the next pair. Spreading practice across eight weak keys gives too few repetitions of each for any of them to consolidate.

Frequently asked questions

Why has my typing speed stopped improving?: Common letters are already automatic, so general practice adds nothing. The remaining time is being lost on symbols and the number row, which ordinary text barely exercises.
What is a good intermediate typing speed for a developer?: Around 60 to 70 WPM on code with accuracy above 97 percent is comfortably sufficient for professional work. Expect your code speed to sit well below your prose speed.
Should I move to advanced snippets?: Only once accuracy is consistently above 97 percent here. Advanced material is symbol-saturated, and practising it at low accuracy rehearses mistakes rather than technique.

Practise by language

JavaScript TypeScript Python C++Go Rust