This post contains no medical advice. If your hands hurt, see a doctor — that's the actual first step, and no software substitutes for it. What follows is a workflow question: if wrist or hand pain from typing means you need to cut your daily keystroke count substantially, what does that setup look like on a Mac, and what does it cost you in practice?

Somewhere between 50% and 70% of programmers deal with repetitive strain injury at some point. The risk factors are unremarkable and unavoidable in the job — long hours at a keyboard, constant mouse use, deadline pressure that keeps you there.

The arithmetic

The reason voice typing helps isn't subtle. It's a volume problem.

An average typist runs about 40 words per minute; professionals hit 65 to 75. Speaking runs 120 to 160 words per minute — 150 is the number you'll see cited most. Stanford HCI research measured speech input at 2.93 times faster than keyboard entry for English.

For wrists, the interesting number isn't speed — it's keystrokes eliminated. A 500-word Slack thread, a PR description, a design doc, a batch of code review comments: that's several thousand keystrokes a day that simply don't happen if you dictate them. You can check your own numbers with our voice vs typing calculator.

The work that moves easiest is prose, and knowledge workers write far more prose than they think: commit messages, PR descriptions, review comments, docs, Slack, email, tickets, meeting notes. For most engineers that's the majority of daily keystrokes. The code itself is a smaller share than it feels like.

What actually transfers to voice

Moves well: Slack and email. PR descriptions and commit messages. Code review comments. Design docs and RFCs. Ticket descriptions. Prompts to coding agents — often better by voice, because you ramble usefully and provide context you'd have edited out while typing.

Moves badly: Code itself. Dictating for (let i = 0; i < arr.length; i++) is worse than typing it, and anyone claiming otherwise hasn't tried it on a real codebase. Terminal commands. Anything where exact punctuation and symbols carry the meaning.

Doesn't move at all: Navigation, selection, window management. Dictation types text; it doesn't drive the machine. If you need hands-free control, that's macOS Voice Control under Accessibility settings — a different tool solving a different problem. People with severe RSI often run both.

A voice typing setup that works on a Mac

Make it local and fast. If dictation takes three seconds and a network round trip, you won't use it, and a tool you don't use protects nothing. Vext runs Parakeet TDT v3 on-device through FluidAudio on Apple Silicon, so there's no upload and no cloud latency.

Use a shortcut you can hit without strain. This matters more than it sounds when your hands are the problem. Vext supports a hands-free toggle on Right-Cmd — press once to start, press again to stop, rather than holding a key down for a whole paragraph. Holding a modifier for ninety seconds is exactly the kind of sustained load you're trying to avoid. Mouse-button bindings work too, which was part of the 1.4.0 hotkey work.

Set per-app styles so you don't edit afterwards. Editing with a keyboard defeats the purpose. Vext's dictation styles — As spoken, Clean up, Email, Message, Bullet points, Formal, Custom — can be bound per application. Slack gets Message, your mail client gets Email, your terminal gets As spoken. Speak once, get text that's already shaped right, and don't touch the keyboard to fix it.

Teach it your vocabulary. Every correction you make by hand is keystrokes you were trying to avoid. Add your project names, dependencies, and colleagues' names to the custom vocabulary once, and stop retyping them.

Watch for the substitution trap. Voice work has its own load — vocal strain and fatigue are real. Alternating between voice and typing distributes the work; going all-voice for eight hours just moves the problem. More on the general setup in hands-free dictation on a Mac.

brew install muvon/tap/vext

The parts nobody mentions

Open offices are hostile to this. You'll feel self-conscious, and you'll be audible to colleagues. Some people solve it with a headset mic and a quiet speaking voice; some negotiate a room; some can't solve it and dictate only from home. It's the most common reason people abandon voice typing, and it has nothing to do with the software.

Accuracy at speed takes practice. Speaking in complete, punctuated thoughts is a skill. The first week is worse than typing. Around week two it stops feeling like work.

Cloud tools reintroduce a different problem. If you're dictating medical details, client information, or anything under NDA, a subscription tool that uploads audio trades one constraint for another. Local processing keeps that door closed.

Being straight about it

Voice typing is not a treatment. It doesn't heal tendons, and using it while ignoring pain is a bad plan. What it does is reduce the mechanical load of one specific activity — text entry — and for most knowledge workers, that's where the bulk of daily keystrokes go.

For people who've had to reduce typing sharply, that's often the difference between working a full day and not. That's a workflow tool doing its job, not a cure, and it's worth being precise about the distinction.

Vext is $49 once, with a 100-dictation trial, on macOS 14+ with Apple Silicon. Everything runs locally.