How to say a dot for member access when dictating
Say “dot”, “period” or “full stop” to produce a period that binds on both sides, so “user dot name” lands as user.name with no spaces. The same lookup applies inside an English sentence, which means the word dot spoken in prose also becomes a period — a real limit worth knowing before you dictate a comment.
An eleven-word chained access costs about 13 seconds of typing against about 4 seconds of speech. (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.)
user.profile.display name.trim()This tool runs entirely in your browser. Nothing you type is sent anywhere, stored, or logged.
Step by step
- 1
Say the object, then “dot”, then the member
Speak the chain as one sentence. The period attaches on both sides, so user dot name arrives as user.name with the two identifiers pulled tight against the separator.
- 2
Chain as far as you like
Keep saying “dot” between links. Each one is an independent table lookup, so a four-link chain needs no pauses and produces the same output every time you say it.
- 3
Watch for the word in prose
Turn Developer Mode off before dictating an English paragraph that contains the word dot. VoiceGem converts the word wherever it appears, because the table matches phrases and does not judge whether you were writing prose.
- 4
By hand
Press the period key. It is unmodified on every common layout and is one of the cheapest characters to type, so a single member access is not a case for dictation.
The period is where prose and code collide, and VoiceGem does not hide it
Unrecognised words pass through the Deterministic Pass untouched, which is why dictating an English sentence into a code comment mostly works. The exception is a word that happens to be in the table, and “dot” is the one people hit: the sentence “a dot product is a scalar” comes back as a.product is a scalar.
Naming the limit is more useful than engineering around it. A table that tried to decide when “dot” meant punctuation would be making exactly the guess the Deterministic Pass exists to avoid, and it would be wrong occasionally in a way you could not predict. The fix is a mode switch, which VoiceGem does per application and per website.
Where the manual way breaks
A single dot is one keystroke and nobody should dictate one. The keyboard wins outright on the individual character and the honest framing is that it always will.
Long chains are the case that changes. A four-link method chain with a call at the end is around forty keystrokes across several hand positions, and it is one spoken sentence in VoiceGem. Say the chain, then type the fixes — that split is where dictation actually earns its place rather than where a demo says it does.
Doing this somewhere else? speech-to-code converter, on your own input, the backslash in an escape sequence, the colon in a type annotation, step by step, or how the comma in an argument list works.
Common questions
Yes. Three phrasings map to the period in VoiceGem's table: “dot”, “period” and “full stop”. All three produce the same character with the same spacing.
Say the digits with “dot” between them, as in “3 dot 14”. Digits pass through as digits, and the period binds on both sides, so the literal comes out closed up.
Switch out of Developer Mode first. VoiceGem's mode system can do that per application, so a comment written in a different app or with the mode off keeps the word intact.
Try the collision yourself and see exactly what comes back.
Open the tool