Skip to main content
EN
Programming

How to Type Symbols and Brackets Without Looking

Symbols sit at the keyboard edges and use your weakest fingers. Here is a systematic way to make those reaches automatic.

5 min read

Almost every typist who can touch-type letters still looks down for symbols. It is the most common gap in an otherwise solid technique, and it is unusually quick to fix.

Why symbols resist practice

Three things make symbols harder than letters:

They live at the edges. The keyboard’s perimeter is worked by the pinkies — the weakest, least dextrous fingers, with the longest reaches.

They need shift. Most symbols are the shifted form of another key, so each one is a two-key coordination rather than a single press.

They have no shape. You type the as one learned motion. There is no equivalent chunk for ){; — every symbol sequence is assembled from scratch.

Learn pairs, not characters

The most useful shift in approach: delimiters travel in pairs, so train them as pairs.

(), [], {}, <>, "", '' — in each case the opening and closing characters are different reaches, frequently on different hands. Drilling ( alone and ) alone, then hoping they combine, is much slower than drilling () as one unit from the start.

The same applies to multi-character operators. => is not = followed by >; it should become a single gesture, the way th is.

A workable order

Learn them in order of how often you use them, not left to right along the keyboard:

  1. Period, comma, semicolon, colon. High frequency, easy reaches, and mostly unshifted.
  2. Parentheses. The most common paired delimiter in almost every language.
  3. Quotes and apostrophes. Constant in both prose and code.
  4. Braces and brackets. Essential for code, rare in prose.
  5. Operators: =, +, -, <, >, !, &, |.
  6. The awkward remainder: ~, `, ^, \, @, #, $, %.

Do not try to learn all of them at once. Three or four at a time, until each is automatic.

Keep your hands anchored

The failure mode with symbols is hand displacement: you lift the whole hand, hunt for {, and land back on the home row slightly off-position. The next several characters are then wrong for reasons that have nothing to do with the symbol.

The index fingers should stay in contact with F and J as much as possible, letting the pinky and ring fingers stretch. If your whole hand moves, the reach is too large — which usually means the wrong finger was assigned to it.

Layout matters more than you would expect

Symbol positions vary considerably between ANSI (US), ISO (UK/EU) and locale-specific layouts. The ISO layout has an extra key next to the left shift; Brazilian ABNT2 places several symbols differently again, and some require AltGr.

Practise on the layout you actually use every day. Muscle memory for symbols is highly position-specific, and training on the wrong layout can be worse than not training at all.

How long it takes

The symbol set is small — perhaps thirty keys, most of which you already half-know. Most people report a clear difference after one to two weeks of short daily sessions.

That makes it one of the highest-return things a competent typist can practise. The alphabet took months; this takes days, and it removes a disproportionate share of the friction from technical writing and code.

Where to start

Symbol typing practice drills the reaches in isolation, deliberately without prose to hide behind.

Once individual symbols are comfortable, move to real syntax where they appear in context: programming typing practice uses genuine code tokens, and the number row practice covers the digits that share those same shifted keys.

Related typing modes

Related articles