Email & URL Character Drill
@ . / : - _ ? = &
Every passage contains: @ . / : - _ ? = &
QWERTY layout assumed. Backspace corrects; uncorrected errors count against net WPM.
An address like first.last@work.net or a link like https://site.com/page/ never gives the hand a break. Ordinary prose treats a period or a comma as the end of a small unit, with a space arriving right after it to reset the hand before the next word starts. Nothing in an address or a link works that way — the period after first and the one after last sit inside one unbroken run of characters, no wider apart than the letters on either side of them, and nothing in the string closes anything off until the whole thing ends.
Nine characters make up this drill's required set — @ . / : - _ ? = & — and most of them cluster on a single finger. The forward slash, the colon, the hyphen, the underscore, the question mark and the equals sign are all produced by the right pinky, distinguished from one another only by whether Shift is held alongside the press. The period sits one finger over, on the right ring finger, still unshifted. Only two characters in the whole set ask for anything else: @ reaches the left ring finger's number-row key while the right hand supplies Shift, and & reaches the right index finger's key while the left hand supplies Shift instead.
That leaves a passage built almost entirely from one finger cycling through six different shift states in sequence, interrupted twice by short detours to the opposite hand, with no space anywhere to recover in between.
Why This Drill
Because six of this drill's nine characters share one finger, the skill being tested isn't reach at all — it's whether that finger can tell, character by character, which of six shift states is coming next, with no travel time between one press and the one after it. A slip here doesn't announce itself the way a misspelled word does; help@team.co typed as help@team,co still looks like a plausible string at a glance and only fails once someone tries to use it.
The two characters that break the right-pinky pattern matter for a different reason. @ and & sit far enough from the rest of the set that landing on either one takes a real decision to leave the run the hand has settled into. ?a=1&b=2 asks for one of each kind — a shifted press and an unshifted one, from both hands — inside eight characters with nothing separating them.
The underscore is worth calling out on its own. In a reference code like the ones the Mixed Alphanumeric Drill covers, an underscore is one arbitrary separator among several. Here it does a job a hyphen in this same passage doesn't: top-level uses its hyphen the way the Hyphen & Dash Drill treats a joining mark between two words, while one_two and _id_ use the underscore to stand in for a plain space that an address isn't allowed to contain at all.
Six Characters, One Finger, Six Different Shift States
/, :, -, _, ? and = are all produced by the right pinky working the same small cluster of keys at the number row's edge, with Shift as the only thing that changes from one to the next — held for a colon, an underscore or a question mark, released for a slash, a hyphen or an equals sign. The Semicolon & Colon Drill isolates exactly one of these six shift decisions on its own; this passage asks the same finger to make all six, back to back, inside strings that never pause to let it reset.
Two Detours to the Opposite Hand
@ and & are the only characters here that don't belong to the right pinky's cluster. @ sits above the 2 key, reached by the left ring finger while the right hand holds Shift; & sits above the 7, reached by the right index finger while the left hand holds Shift. Both interrupt a run the hand has otherwise settled into, which is why a query string like ?a=1&b=2 feels harder than its length suggests — it opens with a right-pinky shift for the question mark, drops into unshifted digits and letters, then demands the one different reach in the whole set before returning to where it started.
A String With Nowhere to Land
https://site.com/page/ contains three slashes, two periods and a colon and not one space across its whole length. Ordinary sentence punctuation is never asked to do this — a comma, a colon, even a hyphen in a compound word sits between letters that give the hand a rhythm to settle into, and a space eventually closes the unit off. An address doesn't close anything until the string itself ends, so every character in it has to land correctly with no natural checkpoint along the way.
A Separator Standing In for a Space That Isn't Allowed
one_two and _id_ use the underscore for a job none of this site's other punctuation drills give it: covering for a space the format simply won't accept. A web address or a variable name can't contain a literal space, so where a title or a sentence would use one, an address uses this mark instead — not meaningless the way the Mixed Alphanumeric Drill treats an arbitrary separator, but doing real, specific work a space would otherwise do.
Frequently Asked Questions
Why does typing an email address or a URL feel harder than typing an ordinary sentence of the same length?
There's no space anywhere in the string to give the hand a pause, and most of the punctuation involved comes from one finger working through a series of different Shift decisions in a row, so a slip has nowhere to be caught before the next character arrives.
Why do @ and & stand out from the rest of this drill's characters?
They're the only two not produced by the right pinky. @ reaches the left ring finger's number-row key with the right hand supplying Shift, and & reaches the right index finger's key with the left hand supplying Shift, so both break a rhythm the rest of the set otherwise settles into.
Does the underscore in an address do the same job as a hyphen?
No. In "top-level" the hyphen joins two words; in "one_two" the underscore is standing in for a space the format forbids.
Why does a single mistyped character in a URL matter more than a typo in a sentence?
A misspelled English word usually still reads as recognisably wrong. A mistyped address just fails silently — site.com/pgae/ looks like a perfectly reasonable string at a glance and only reveals the error when someone tries to follow it.
Is the colon in http: the same keystroke as the colon in a time like 14:51?
The same key and the same finger, but a different role — here it's followed immediately by two slashes with no digit anywhere nearby, and it only ever appears once, near the start of the string, rather than potentially several times through a longer passage.
Most people paste links rather than typing them out — is this drill still worth the time?
Plenty of ordinary tasks still call for typing these characters from scratch — a markdown-style link, a contact form, a server path entered by hand — and the Symbols for Coders lesson covers some of the same characters in a different setting if this drill's focus on addresses isn't the immediate need.