May 16, 2026

Fixing RSI: How I Switched From Typing to Dictation Without Going Insane

Six months ago, typing became painful. Not “I should take more breaks” painful — “I cannot finish this email without my forearms burning” painful. I am a software developer. I type for a living. The prospect of losing that ability was terrifying. This is the story of how I switched to dictation, what I wish I had known at the start, and what actually worked.

The moment I knew I had to switch

RSI does not announce itself. It accumulates. For me, it was months of mild discomfort that I ignored — typing through it, telling myself it would go away, buying a vertical mouse and an ergonomic keyboard and pretending those would fix it. They did not.

The wake-up call was a Monday morning. I sat down at my desk, opened Slack, and could not type a response. My forearms felt like they were full of hot sand. I had deadlines. I had PRs to review. I had meetings to prepare for. And I could not type.

If you are reading this because you are in a similar position, I want you to know: you can still work. You can still be productive. It will be weird and frustrating at first, and then it will not be. Here is the path.

What I tried first (and why it mostly did not work)

Ergonomic keyboards

I bought a split mechanical keyboard. I bought a Kinesis Advantage. I tried a trackball, a vertical mouse, a pen tablet. Every single one of these helped marginally, and none of them solved the problem. If your RSI is moderate to severe, rearranging the furniture does not fix the fire. Ergonomics are prevention, not treatment.

Apple Dictation

Apple's built-in dictation is fine for short messages. It is not fine for writing anything longer than a text. The accuracy is mediocre. The formatting is nonexistent. There is no cleanup — what you say is what you get, complete with every “um” and false start. I used it for about three days before I started looking for alternatives.

Cloud dictation services

Wispr Flow and Aqua Voice are genuinely good products. The accuracy is excellent. The formatting is smart. But I work with code and internal company documents, and sending all of my professional communication through a third-party server was not acceptable to my employer — and honestly, not acceptable to me either. When your voice data includes discussions of architecture decisions, bug reports, and internal project names, cloud processing is a non-starter.

What actually worked: on-device dictation

On-device dictation — Rewisper, specifically — turned out to be the answer. The model runs on my Mac's Neural Engine. Audio is processed locally and never leaves the machine. The accuracy is strong enough for professional communication. And the formatting pipeline handles the cleanup that Apple Dictation does not.

But the tool was only half the battle. The other half was retraining myself to communicate by voice. That took longer than I expected, and it is where most people give up.

The adjustment period: what the first month actually feels like

Week 1: Everything is terrible

You will hate dictation in the first week. You will feel stupid talking to your screen. Your dictated sentences will be halting and incoherent. You will forget the hotkey five times an hour. You will accidentally dictate while your microphone is muted and not notice until you look at the screen and see nothing. Every message will take twice as long as typing. You will wonder if this is worth it.

This is normal. Push through it. The only way out is through.

Week 2: The hotkey becomes muscle memory

Somewhere around day five, you stop thinking about the hotkey. Your thumb finds it automatically. You start dictating without the internal “I am now going to dictate” preamble. The self-consciousness is still there, but it is fading.

Key discovery: speaking is a different cognitive mode than typing. Your sentences come out longer and more complex when you speak them. This is good for the quality of your communication but bad for your editing burden. You learn to rein it in.

Week 3: The speed catches up

By the third week, dictation is faster than typing for most communication tasks. Slack messages, emails, PR descriptions, documentation — all of these come out faster and better by voice than they did by keyboard. You still type for code and terminal commands, but that is maybe 30% of your day. The other 70% is voice.

Week 4: You stop thinking about it

This is the milestone that matters. By week four, dictation is not a coping strategy or a workaround — it is just how you write. You do not think “I am dictating now.” You think “I need to respond to this message” and you do it. The medium has become transparent.

The hybrid workflow: voice for prose, keyboard for code

I never stopped typing entirely. I type code, terminal commands, and keyboard shortcuts. The goal was never to replace the keyboard — it was to offload the 60-70% of my work that is communication rather than coding. That is where the volume is, and that is where the pain was.

A typical workday now looks like this:

• Slack and email: 100% dictation. I hold Control+Option+Space, say what I need, and it appears.
• PR descriptions and code reviews: Dictation for the prose, keyboard for inline code references.
• Documentation: 100% dictation. This is where the speed difference is most dramatic.
• Coding: 100% keyboard. Code is not a spoken language.
• Terminal: 100% keyboard.

The important thing is that my typing load dropped by about 70%. That was enough. The pain did not disappear overnight, but it stopped getting worse, and over weeks it began to recede. By reducing the total keyboard time, I gave my arms room to recover while still doing my job.

Practical tips for the RSI-to-dictation switch

The mental health side of RSI

Nobody talks about this, so I will. Losing the ability to type when your career depends on it is existentially frightening. For several weeks, I was genuinely scared that I would not be able to continue working as a developer. That fear is corrosive. It makes the pain worse because you are physically tense all the time, which aggravates RSI in a vicious cycle.

Finding dictation was not just a productivity win — it was a mental health intervention. Knowing that I had an alternative to typing meant I could stop panicking about my career and start focusing on recovery. The fear receded, the tension dropped, and the pain followed.

If you are in that place right now — scared, in pain, wondering if you can keep doing your job — I want you to know that dictation works. It is awkward at first. It takes practice. But it works. And knowing you have an alternative makes everything else easier.

The bottom line

RSI forced me to switch from typing to dictation. I wish I had done it sooner, before the pain forced the issue. Dictation is faster for most communication tasks, produces better-structured prose, and — critically for anyone with RSI — lets you keep working while your hands recover.

The adjustment period is real. The first week is terrible. The second week is awkward. By the fourth week, you will have a new skill that makes you more productive than you were before the pain started. And you will have your hands back.

If you are dealing with RSI and want to try this path: get an on-device dictation tool so your voice data stays private, start with short messages, keep typing for code, and give yourself a full month before you decide whether it works. The technology is ready. The question is whether you are patient enough to get through the awkward beginning. I nearly was not. I am glad I did.

Read: How I Write 3x Faster Using Dictation (As a Developer Who Hates Voice Assistants) →