Build a developer dictation vocabulary
Start with terms you repeatedly correct: product names, repository names, acronyms, and domain language. Add a small set to WhisperJot's vocabulary, dictate each in a sentence, and compare the result. Use text shortcuts for longer fixed expansions when appropriate.
By WhisperJot · Documentation reviewed
Choose terms from actual corrections
A large speculative word list is harder to maintain than a short list of words you really use. Capture the intended spelling and the mistaken output from a few normal dictations. Start with five terms, then add more only when repeated errors justify it.
| Term type | Example | Check |
|---|---|---|
| Product name | WhisperJot | Capitalization and word boundary |
| Database | PostgreSQL | Exact spelling in a sentence |
| Repository | billing-worker | Hyphen and repository identity |
| Identifier | user_id | Underscore and case; type exactly if needed |
Add words and test them in context
These are practice sentences, not measured recognition results. Vocabulary is a correction aid, not a guarantee that code identifiers, capitalization, or punctuation will always be exact.
- Choose a vocabulary word entry and enter the intended spelling. Save it.
- Dictate a sentence that uses the term naturally, rather than reading only an isolated name.
- Repeat with the same engine and cleanup setting. Compare the output with the result before adding the word.
WhisperJot should insert the release note into the editor. PostgreSQL stores the account record. Check the billing-worker repository before changing the retry policy.
Use shortcuts for fixed text
A word entry and a text shortcut solve different problems. Use a word entry for a name you say in normal prose. Use a distinctive shortcut phrase when you want a saved block of text. Avoid common trigger phrases that could expand during an unrelated message.
- Try a shortcut in a scratch document before using it in chat or email.
- Review any expansion that contains a date, version, or other changing fact.
- Keep exact paths and commands in a reliable copyable source instead of relying on recognition alone.
Questions
Will custom vocabulary make code dictation exact?
No. Recognition can still change punctuation, spacing, and case. Vocabulary is useful for technical prose, but review executable code and exact identifiers independently.
Should every technical word be a shortcut?
No. Use vocabulary words for spelling support and shortcuts for deliberate fixed expansions. A common technical term is usually a poor trigger for a long block of text.
Sources and related guides
Product behavior is based on the documentation below, reviewed 2026-09-09. Examples are authored illustrations; measurement worksheets are for your own observations.