TypeScript typing test
Generics, type annotations, and angle brackets that wreck your WPM.
Characters that slow you down in TypeScript
< >Shift-comma and shift-period. Adjacent keys, same hand.|Shift-backslash — a right little-finger stretch past Enter.:Shift-semicolon, right little finger, once per annotation.?:Optional properties: question mark straight into a colon.=>Inherited from JavaScript and just as frequent here.
Generics live on two awkward keys
Angle brackets are everywhere in TypeScript, and they are shift-comma and shift-period: two adjacent keys needing the same hand to open and close cleanly. A record type, a promise, an array of a type parameter — all of them.
The common failure is not the bracket but the pair. Typing the opener correctly and then reaching for the closer after a word of content is where rhythm breaks, because your hand has moved in between. Drill whole generic expressions, never single characters.
The pipe is the most-missed key in TypeScript
Union types make the pipe a routine character. It sits on shift-backslash, above Enter, and it is one of the longest reaches your right little finger makes in any language.
It is also frequently typed with the wrong finger — people curl the ring finger over rather than extending the little finger, which works at low speed and falls apart at pace. If unions appear often in your code, this single key is worth a session on its own.
Colons appear far more often than in JavaScript
Every annotation, every interface field, every object type adds a colon. In plain JavaScript the colon is occasional; in TypeScript it is structural, and it is a shifted right little-finger key.
Because the colon and semicolon share a key, interface bodies alternate shift and no-shift on the same finger repeatedly. That alternation is the specific thing to practise — it is considerably harder than either character alone.
Type-heavy code rewards accuracy over speed
A mistyped identifier in JavaScript often still runs. A mistyped type annotation stops the build, and you find out immediately. In practice that means TypeScript punishes error rate more than raw pace.
Track accuracy on these drills rather than WPM. Above 97 percent on TypeScript snippets, speed follows on its own; below it, pushing pace only adds compile errors.
Frequently asked questions
- What makes TypeScript harder to type than JavaScript?
- Angle brackets, colons, pipes and question marks appear constantly, and all four are shifted characters on the edges of the keyboard rather than in the comfortable letter zone.
- How do I get faster at typing generics?
- Practise complete expressions rather than the brackets alone. The difficulty is returning to the closing bracket after your hand has moved through the content, not the bracket itself.
- Should I practise TypeScript or JavaScript?
- Whichever you actually write. If you write both, TypeScript is the better drill — it contains the JavaScript syntax plus the annotation layer on top.