Dictation for developers: use your voice for the prose, not the code
Nobody sensible dictates a for loop. But a working developer types a surprising amount of plain English every day: commit bodies, pull request descriptions, review comments, design notes, tickets, and long prompts for coding assistants. That prose is where dictation pays off. This guide splits the job into what to speak and what to keep typing, gives example sentences for each case, and is blunt about where speech recognition breaks down on technical text.
Speak it or type it: a quick sorting rule
The rule of thumb: if a colleague could read it aloud without spelling anything, dictate it. If it contains identifiers, punctuation-heavy syntax or exact strings, type it. Most real tasks are a mix, so you dictate the sentences and type the few tokens inside them.
| Task | Dictate? | Why |
|---|---|---|
| Commit message body | Yes | Two or three sentences of reasoning, mostly plain words |
| Commit subject line | Usually | Short; type the file or function name afterwards |
| Code review comment | Yes | Explaining a concern is faster spoken than typed |
| README and how-to docs | Yes, for the prose | Type code blocks, commands and paths by hand |
| Prompt for a coding assistant | Yes | Long context is where speaking beats typing most |
| Variable names, function calls | No | camelCase, underscores and brackets come out wrong |
| Shell commands, flags, regex | No | One wrong character changes the meaning |
| File paths and URLs | No | Slashes and dots are tedious to speak and easy to misplace |
Commit messages by voice
Run git commit without the -m flag so your editor opens. Type the subject line, or dictate it and fix the names, then leave one blank line and dictate the body. The body is the part people skip when typing because it feels like a chore, and it is exactly the part that explains the change to whoever runs git blame in a year.
A body you can say in about fifteen seconds: “The retry loop gave up after the first timeout because the counter was reset inside the catch block period. Moved the reset before the loop and added a test that simulates two timeouts in a row period.” Then type the test file name if you want it there.
Commit-message conventions differ by team, so check yours: many teams keep the subject short and in the imperative (“Fix retry counter reset”) and wrap the body. Dictation does not care about wrapping; reflow in the editor before saving.
Review comments that read well
Typed review comments tend to be terse, and terse comments read as rude. Spoken ones come out closer to how you would say it at the next desk. A useful shape is: what you noticed, why it matters, what you suggest.
Example to dictate: “This query runs once per item in the list comma so a page with two hundred orders makes two hundred round trips period. Could we load them in one call and group in memory question mark. Happy to pair on it if useful period.” Then click back into the comment and wrap the function name in backticks by hand.
Read each comment once before posting. Recognition errors in review comments are worse than in a private note, because the author has to guess what you meant.
Docs, design notes and tickets
Documentation is where developers have the most to say and the least patience to type it. Try this split: dictate the explanation section by section (“what this service does”, “how to run it locally”, “what breaks most often”), and type every command, environment variable and code fence afterwards. A first draft spoken in ten minutes, then edited, usually beats an empty README that waits for a free afternoon.
For tickets and bug reports, speak the reproduction steps as numbered sentences: “Step one comma open the settings page period. Step two comma change the time zone and save period. Expected the dashboard to update comma it still shows the old zone period.” You will clean the numbering up in seconds, and the details you would have skipped while typing are there.
Prompts for coding assistants
Coding assistants do better with context: what you are trying to do, what you already tried, what must not change. Typing all of that is slow, so people write one line and get a generic answer. Speaking it takes under a minute.
Dictate the context in plain words, then paste the code or error message by hand, because stack traces and code should be copied exactly, never spoken. A full walkthrough of structuring prompts by voice, including the trap where a spoken new line sends the message early, is in our guide to dictating prompts to ChatGPT and Claude.
What dictation is bad at (and the few workarounds)
- Identifiers. “get user by id” arrives as four words. On Mac, Apple's dictation commands include “no space on” and “no space off” to join the next phrase, plus “caps on” for Title Case, but combining them into camelCase by voice is slower than typing.
- Symbols in bulk. Both Apple and Microsoft let you say “open parenthesis”, “underscore” or “backslash”. Windows 11 voice typing even lists “backtick” for English. Fine for one symbol, painful for a line of code.
- Jargon and product names. Library names, internal service names and acronyms are the most common misheard words. Type them, or dictate around them and fill the gap.
- Exactness. A misheard word in a comment is a typo. A misheard character in a config value is a bug. Never dictate values that get executed or parsed.
- Open-plan offices. Talking to your computer all day next to teammates on calls is awkward for everyone. Push-to-talk and a headset microphone help; a quiet room helps more.
Exact command names for punctuation and formatting on each system are collected in how to dictate punctuation.
Setting it up so it does not get in the way
Developers switch apps constantly: editor, terminal, browser, chat. Whatever tool you use, it should write wherever the cursor is, in every one of those apps, with one gesture. Built-in Mac Dictation and Windows voice typing both write at the cursor, though Windows voice typing needs an internet connection and Mac Dictation stops after 30 seconds without speech.
Voice Monkeys is a dedicated option built around that gesture: hold the right Option key on a Mac (right Alt on Windows and Linux), speak, release, and the text lands at the cursor, including in a terminal or an IDE. A quick tap keeps it listening until the next tap, and Esc cancels. On Apple Silicon Macs the speech model runs on the Mac itself, so audio never leaves the machine; if your employer has rules about where work audio may go, that is a fact to check against them, not a substitute for asking. On Linux it needs an X11 session rather than Wayland. You can download it and try it for 7 days. If you mostly write prose and rarely leave one editor, the built-in tools may be all you need.
Questions and answers
Can I write code with voice dictation?
General dictation tools are poor at code: identifiers, brackets and exact syntax come out wrong. They work well for the prose around code, such as commit bodies, comments in reviews, docs and prompts.
How do I dictate a commit message?
Run git commit without -m so your editor opens, type or dictate a short subject, leave a blank line, then dictate the body. Fix file and function names by hand before saving.
Does dictation work in a terminal?
Tools that type at the cursor, including Mac Dictation, Windows voice typing and dedicated apps like Voice Monkeys, write into the terminal like a keyboard would. Do not dictate commands you are about to run; type those.
How do I dictate symbols like underscores or brackets?
Say the symbol's name, for example “underscore” or “open square bracket”. Apple and Microsoft publish lists of these commands; they differ slightly between systems and languages.
Is it safe to dictate work code descriptions?
That depends on where the speech is processed and on your employer's rules. Check whether your tool processes audio on the device or on a server, then check your company policy.
Sources
- Apple: Commands for dictating text on Mac (checked November 6, 2026)
- Apple: Use Dictation on Mac (checked November 6, 2026)
- Microsoft: Use voice typing to talk instead of type on your PC (checked November 6, 2026)