Code typing test — type keywords, brackets and symbolsTypeRush

Why a code test is a different test

An ordinary typing test is built from common lowercase English words, which means it mostly measures how fast your fingers move around the home row. Code does not live there. It lives on the symbol row and the shift key: =>, !==, ();, &&, closing braces, underscores, and identifiers with a capital letter buried in the middle of them. Those are different motor patterns with different failure modes, and being fast at prose predicts them surprisingly poorly.

The passage here is drawn from a pool of real code tokens — keywords, punctuation clusters, bracket pairs, camelCase and CONSTANT_CASE identifiers, method chains, string literals, and type annotations. It is deliberately not a compilable program. A real snippet lets you coast on recognition: once you see the shape of a familiar function you stop reading and start recalling. A shuffled token stream forces you to actually type what is in front of you, which is the thing being measured.

Expect a lower number than your prose score, and do not treat that as a failure — reaching for a bracket costs more than typing another vowel. Your code bests are stored separately from your prose bests for exactly that reason, so a run here never quietly overwrites or undercuts the score on the standard test.