Saying a greater-than sign out loud when dictating code
Say “greater than” or “close angle” to produce >. Spacing is kept on both sides, so “if count greater than zero” gives if count > zero — correct for a comparison. Closing a generic or a tag with the same phrase leaves a space before the bracket that your formatter will need to remove.
A nine-word guard condition costs roughly 10 seconds typed against roughly 3.3 seconds spoken. (sources: Dhakal, Feit, Kristensson & Oulasvirta, “Observations on Typing from 136 Million Keystrokes”, CHI 2018, 168,000 participants, 136 million keystrokes; Yuan, Liberman & Cieri, “Towards an Integrated Understanding of Speaking Rate in Conversation”, Interspeech 2006, 2,438 American English telephone conversations (Switchboard corpus). The speech figure is conversational rate, not a measured dictation rate — no such measurement exists.)
if retry count > max attempts {This tool runs entirely in your browser. Nothing you type is sent anywhere, stored, or logged.
Step by step
- 1
Say the comparison naturally
Speak both operands with “greater than” between them. The character keeps its spaces, so the result reads the way a formatter would leave a comparison.
- 2
Build a compound operator from two entries
Say “greater than equals” for >=. VoiceGem has no single entry for the compound; it comes out of two independent lookups whose spacing happens to sit right next to each other.
- 3
Close generics with “close angle”
Use the bracket phrasing when you are ending a type parameter list. Output is identical either way, and the trailing space before the bracket is expected.
- 4
The keyboard route
Press Shift-period. Anyone writing shell redirection or generics reaches this chord constantly and will beat dictation on a single character.
Compound comparison operators are composed, not enumerated
VoiceGem's table has forty distinct symbols and no entry for >= at all. Saying “greater than equals” produces two lookups in sequence, and because both characters attach on neither side, the pair arrives adjacent in the output.
Keeping the table small is what makes it learnable. A table with an entry for every operator pair would run to several hundred phrases and nobody would read it; forty symbols plus composition covers the same ground and fits on one reference page. The Deterministic Pass never needs to know that >= is a single operator, because it never parses.
Where doing it by hand breaks down
Shift-period is a chord a developer already owns and a single comparison is not worth dictating. The honest baseline is that the keyboard wins on individual characters, always.
Boolean conditions with several clauses are the shape that costs. Three comparisons joined by logical operators means six shifted characters interleaved with identifiers, and the failure mode of typing it is an inverted comparison you do not notice until a test fails. Dictating the condition in VoiceGem produces the same operators in the same places on every run.
Doing this somewhere else? the browser-based spoken-symbol reference, what changes for the double equals comparison, the assignment equals sign, or the less-than sign and opening angle bracket.
Common questions
Say “greater than equals”. VoiceGem produces >= from two separate table entries, because both characters keep their spacing and land adjacent.
No. Both phrases map to the same character with the same attach flags, so the spacing is identical either way.
Yes. Say “greater than” between the command and the filename. The character keeps its spaces, which is how a shell line is normally written anyway.
Read the whole table and see which operators are composed rather than listed.
Open the tool