Repetitive strain injury (RSI) doesn't announce itself. Most developers ignore the early warning signs — aching wrists, tingling fingers, that twinge in your right shoulder — until something tears or pinches and you're on a six-week medical leave.
Voice dictation isn't a cure. It's prevention. And it's the single biggest lever a developer has to dramatically reduce daily keystroke load without sacrificing throughput.
This is a practical guide to building voice into a real engineering workflow before you have to.
Why developers are at risk
Modern developers type a lot. A reasonable estimate is 8,000–15,000 keystrokes per day for active engineering work. Add Slack messages, code review comments, design docs, commit messages, and you're often at 20,000+.
Compounded over years, with poor posture, suboptimal keyboard, mouse-heavy navigation, and the steady creep of side projects in the evening — that's the load profile that produces RSI.
The most cited research on RSI in software engineering points to a multi-year onset for most cases. The early symptoms are usually missed or ignored. By the time pain forces a change, structural damage has often already happened.
Three forms of RSI you should know
- Carpal tunnel syndrome — pressure on the median nerve at the wrist. Numbness and tingling in the thumb, index, and middle fingers.
- Cubital tunnel syndrome — compression of the ulnar nerve at the elbow. Tingling in the ring and little fingers.
- De Quervain's tenosynovitis — inflammation of the tendons at the base of the thumb. Pain when gripping or pinching.
Why voice is the highest-leverage intervention
Most RSI advice focuses on ergonomics — split keyboards, vertical mice, standing desks, wrist rests. These help. But they all still involve typing.
Voice dictation is different: it's the only intervention that actually reduces your keystroke count, often by 30–50% for active engineering work. You're not redistributing the load — you're removing it.
The reason this works for developers specifically:
- Most of what you "type" isn't code, it's prose — Slack messages, PR descriptions, code review comments, design docs, commit messages. All highly dictation-friendly.
- The code you do write increasingly comes from AI assistants (Cursor, Claude Code, Copilot). The actual typing happens in the prompt, not the editor.
- Modern dictation accuracy on technical vocabulary is better than people remember. Whisper transcribes function names, library names, and technical jargon correctly when added to a custom dictionary.
A practical setup for developers
You need three things on your Mac:
1. A dictation app that types into any application. We make JustVoice — local Whisper transcription with code dictation mode and IDE detection. There are alternatives (compare them here). What matters is that it's hotkey-triggered, low-latency, and works in any app — IDE, Slack, GitHub, terminal. 2. A hotkey your hand naturally rests on. Right Option is JustVoice's default. We've tried thumb buttons on a mouse, foot pedals, and keyboard chords. Right Option won. Find what works. 3. A custom vocabulary populated with your codebase. Spend 30 minutes adding the names of your services, modules, classes, methods, and any technical terms specific to your stack. This is the single biggest accuracy improvement you'll make.Workflows where voice replaces typing entirely
PR descriptions and code review comments. Average PR description is 100–300 words. Dictating it takes under a minute. Typing it takes five. Slack messages longer than two sentences. Dictate, scan, send. Faster than typing and you're more likely to actually compose something thoughtful. Design docs and ADRs. Dictation is dramatically better for first-draft prose. Edit the typed pass after. Commit messages. Especially for substantial commits where you should explain the why. Dictation makes you more verbose in the right way. AI assistant prompts. This is the one that compounds. Vibe coding rewards verbose, contextual prompts. Typing them is the bottleneck. We covered this in detail in Vibe Coding by Voice on Mac.Workflows where voice supplements typing
Code itself. You can dictate code with code mode (JustVoice Pro detects your IDE and adapts), but most developers find it works best for verbose languages and as a complement to typing rather than a full replacement. Documentation comments. Dictate the prose, type the code references. The hybrid is faster than either alone. Variable and function naming. Sometimes faster to dictate, sometimes faster to type. Develop intuition.Three habits that reduce RSI risk independent of voice
These compound with dictation:
- 30-second pause every 30 minutes. Hands off keyboard. Stand up. Look out a window. Don't power through.
- Check your wrist position. Wrists should be straight or slightly extended downward. Not bent up. Not bent down.
- Mouse less. Learn keyboard shortcuts. The mouse is harder on tendons than the keyboard for most people.
When to actually see a doctor
If you have:
- Persistent tingling or numbness in your hand or fingers
- Pain that wakes you at night
- Weakness or dropped objects
- Pain that radiates from your wrist into your forearm
Get started with voice this week
If you want to try voice dictation today: Download JustVoice for free. 5,000 words a month, no credit card, takes five minutes to set up.
Spend the first week dictating Slack messages and PR descriptions. Spend the second week adding terms to your custom dictionary as you hit them. By week three you'll be measurably reducing your daily keystrokes.
That's the whole intervention. It's also the most effective thing you can do right now to keep typing for another twenty years.
---
Vibe coding by voice on Mac → JustVoice for developers →