Repetitive strain injury is common among people who type for a living, and developers type a lot. It builds slowly: thousands of small movements a day, for years, until wrists or forearms start to ache.

Voice coding won't fix everything, but it's one of the more practical ways to cut keyboard load without losing output. With AI coding agents doing more of the syntax, more of what you type is plain language, and plain language is easy to speak.

Warning

This is general information, not medical advice. If you already have pain, numbness or tingling, see a doctor or physiotherapist. Voice can reduce load; it isn't a treatment.

Why it helps#

Your hands rest

While you speak, your hands are still. No wrist extension, no finger travel.

Fewer repetitions

RSI is linked to repeating the same movements many thousands of times. Each paragraph you speak is a few hundred keystrokes you didn't make.

Less forearm load

Less typing means less work for the forearm muscles that hold your wrists in position.

Built-in breaks

Even if voice covers a third of your input, your hands get regular rest spread across the day.

What to move to voice#

The biggest wins are the long, plain-language things:

Prompts to AI coding agents (Cursor, Claude Code, Codex, Windsurf). Often the largest single source of typing now.
Slack and email
PR descriptions, review comments, tickets
Docs, READMEs, comments

Keep syntax, small edits and navigation on the keyboard. Whisperer writes what you say as text and has no spoken symbol commands. Rather than dictating code, describe the change to an agent and let it write the code. See how to dictate code on Mac.

A gradual start#

Don't try to go all-voice on day one.

Week 1: messages

Slack, Teams, email. Nothing to learn. Whisperer's Match the app setting leaves the full stop off one-line chat messages so replies sound like you.

Week 2: agent prompts

Speak every prompt to your coding agent. This is where most developers' typing goes now.

Week 3: PRs, reviews, docs

All prose. Speak it, paste it in place.

Week 4: find your split

Voice for anything longer than a sentence, keyboard for code and edits. Check Whisperer's Statistics page to see how many words you moved to voice.

Setup that helps#

A decent mic

The built-in Mac mic is fine in a quiet room. A headset helps elsewhere.

Toggle mode

Holding a key is still a hand movement. Toggle mode (press once to start, once to stop) is easier for long dictation.

Personal dictionary

Fewer misheard names means fewer keyboard corrections. Add your libraries, services and teammates.

Live preview

See the words as you speak and catch mistakes before you paste.

Text arrives by paste: Whisperer copies it and shows a Copied ⌘V toast, and you press ⌘V. One keystroke per dictation instead of hundreds.

The 50/50 approach#

Tip

You don't need to abandon the keyboard. Split the work: voice for prompts, messages, docs and reviews; keyboard for editing, navigation and shortcuts. Even a rough 50/50 split removes thousands of keystrokes a day.

Meetings are typing too#

Taking notes during calls is a lot of fast, stressful typing. With Pro, Whisperer records Zoom, Meet, Teams and Slack huddle calls without a bot and writes the notes for you: summary, decisions and action items. See meeting notes.

Other things that help#

Breaks. Short, frequent ones beat long, rare ones. The 20-20-20 rule (every 20 minutes, look 20 feet away for 20 seconds) is a handy reminder to move.
Stretches. Gentle wrist and finger stretches. Ask a physio which ones suit you.
Desk setup. Keyboard at elbow height, wrists straight, screen at eye level.
Keyboard and mouse. Split keyboards and vertical mice help some people keep their wrists neutral.
Your voice. Talking all day has its own strain. Drink water and speak at a normal volume.

Don't wait until it hurts#