How a Developer with RSI Found a New Way to Code

This story is a fictional composite based on real experiences shared by developers in RSI communities. While "Alex" is not a real individual, the symptoms, struggles, and recovery path described here reflect genuine experiences reported by many software developers.

The First Signs

Alex was 32 years old, a full-stack developer with eight years of professional experience. He worked at a mid-sized SaaS company, writing TypeScript during the day and occasionally tinkering with side projects at night. He loved his work. Coding was not just his job — it was how he solved problems, expressed ideas, and built things that mattered.

The first sign came on a Tuesday evening in November. After a long day of refactoring a legacy API, Alex noticed a tingling sensation in his right hand, concentrated in his thumb, index finger, and middle finger. He shook his hand a few times, the feeling passed, and he thought nothing of it.

Over the next few weeks, the tingling came back. Always at the end of long sessions. Always in the same fingers. He started waking up at night with numb hands, needing to shake them until the feeling returned.

"Probably just sleeping on my arm wrong," he told himself.

Pushing Through

Like most developers, Alex was practiced at ignoring his body's signals. Deadlines were pressing. His team was launching a new feature, and he was the lead on the backend. Taking a break was not something that crossed his mind seriously.

The tingling became a dull ache. The ache became a burning sensation that ran from his wrist to his elbow. He started making more typos, not from carelessness but from his fingers not responding the way they should. Simple tasks like opening a jar or turning a doorknob became unexpectedly painful.

He bought a wrist brace at the pharmacy and wore it while typing. It helped a little. He found an article about ergonomic keyboards and ordered a split keyboard. That helped too, for a while.

But the pain kept coming back, and it was getting worse.

The Diagnosis

Three months after the first tingling, Alex finally went to see a doctor. The examination included a nerve conduction study — electrodes on his arm measuring how quickly electrical signals traveled through his median nerve.

The diagnosis: bilateral carpal tunnel syndrome, moderate severity. The doctor also noted signs of extensor tendinopathy in his forearms — inflammation of the tendons on the backs of his wrists from years of mouse use.

"You need to significantly reduce your typing and mouse use," the doctor said. "At least for the next two to three months, while we try conservative treatment."

Alex stared at him. "I'm a software developer. That is literally all I do."

The doctor handed him a referral for physical therapy and a prescription for night splints. "We need to get the inflammation down. If we don't, the next step is cortisone injections, and after that, surgery. Let's try to avoid that."

The Low Point

The next few weeks were the hardest of Alex's career. He wore splints at night and took anti-inflammatory medication. He did the stretches his physical therapist prescribed. He adjusted his workstation according to every ergonomic guide he could find.

But he still had to work. And every hour at the keyboard felt like borrowing against a debt his body could not afford.

He started dreading sprint planning meetings — not because of the meetings themselves, but because every new ticket assigned to him meant more hours of typing, more pain. He began to wonder, seriously, whether he could continue being a developer.

He browsed job listings for non-technical roles. He considered management, product, or technical writing — anything that might involve less typing. But each option felt like a retreat from the work he loved.

The worst part was the isolation. Most of his coworkers did not understand. "Just take more breaks," they said. "Have you tried a standing desk?" The advice was well-meaning but insufficient. His condition was beyond what a standing desk could fix.

Discovering Voice Typing

The turning point came from a Reddit thread. In the r/RSI subreddit, Alex found a post from another developer who had been in a nearly identical situation two years earlier. The post described how they had rebuilt their workflow around voice typing and hands-free tools, and were now coding full-time with minimal pain.

Alex was skeptical. He had tried Windows Voice Typing (Win+H) before and found it clunky and inaccurate, especially with technical terms. He imagined himself shouting "open curly brace" at his monitor and cringing.

But the thread mentioned several tools he had not tried. One that caught his attention was Murmur, a voice typing app that worked in any application with a single shortcut. The comments described it as particularly good for the non-code parts of a developer's day: messages, documentation, emails, code reviews.

He downloaded it and tried dictating a Slack message. He pressed the shortcut, said "Hey team, the API refactoring is going to take longer than expected. I found some edge cases in the authentication flow that need to be addressed before we can merge. I will update the ticket with details," and the text appeared in the Slack input field, correctly transcribed, punctuated, and ready to send.

It was not life-changing in that single moment. But it was surprisingly easy.

The Learning Curve

Alex committed to an experiment: for two weeks, he would use voice typing for all non-code work and track how his pain levels responded.

The first few days were frustrating. Speaking his thoughts instead of typing them felt unnatural. He was self-conscious about talking to his computer, especially in the office. He booked a small meeting room for the first week, telling his team he needed quiet time for focused work.

By day three, he noticed something unexpected: his writing was getting better. When he typed, he tended to write in fragmented, jargon-heavy sentences. When he spoke, he naturally used complete thoughts and clearer language. His documentation was more readable. His code review comments were more helpful.

By the end of week one, he had reduced his typing by an estimated 35 percent. His wrists still hurt during coding sessions, but the evening pain was noticeably less. He was sleeping through the night without numb hands for the first time in months.

By week two, voice typing felt natural for messages, emails, documentation, PR descriptions, and meeting notes. He was not faster than typing yet, but he was comfortable and consistent.

Expanding the Toolkit

Encouraged by the early results, Alex explored deeper. He installed Talon, the open-source voice command system, and spent evenings learning its command vocabulary. Within a few weeks, he could navigate VS Code, switch between files, scroll through code, and even do basic editing by voice.

His setup evolved into a hybrid system:

• Murmur for all natural language input — messages, docs, emails, comments
• Talon for VS Code navigation, window management, and code-specific commands
• Keyboard for precise code editing, but in shorter, more deliberate sessions
• Vertical mouse for minimal, essential mouse work

He also invested in a quality headset microphone, which improved recognition accuracy significantly, and rearranged his schedule to alternate between voice-heavy and keyboard-heavy tasks throughout the day.

Three Months Later

Three months into his voice typing experiment, Alex's daily routine looked radically different:

• Morning standup notes: Dictated with Murmur
• Code reviews: Read code on screen, dictated comments with Murmur
• Coding sessions: 60 to 90 minutes maximum, with 10-minute breaks, using keyboard and vertical mouse
• Slack and email: Almost entirely voice-typed
• Documentation: Entirely voice-typed
• Meetings: Notes dictated in real time

His breakdown was roughly 70 percent voice, 30 percent keyboard. His total keyboard time had dropped from eight-plus hours a day to under three.

The results were tangible:

• Pain reduced by approximately 80 percent. He still had some discomfort during keyboard sessions, but the constant background ache and nighttime numbness were gone.
• Productivity held steady. His sprint velocity was within normal range. His manager noticed no drop in output.
• Writing quality improved. Multiple colleagues commented that his documentation and review comments had gotten clearer.
• Sleep improved dramatically. No more waking with numb hands.

His physical therapist was pleased. The nerve conduction study at his three-month follow-up showed measurable improvement. The doctor noted that surgery was off the table for now.

What Alex Would Tell You

Looking back, Alex wishes he had done several things differently.

Do not ignore early symptoms

"The tingling was a warning, and I treated it like a nuisance. If I had started making changes when the symptoms first appeared, I could have avoided months of pain and the fear that my career was over."

Talk to your team early

"I was embarrassed about my condition. I thought admitting I could not type all day was admitting I was not a real developer. When I finally told my manager, she immediately offered accommodations — a private room for voice work, flexible hours, and budget for ergonomic equipment. I should have spoken up months earlier."

Try voice typing before you need it

"The worst time to learn a new tool is when you are in pain and desperate. If I had tried voice typing when I was healthy, the learning curve would have been much less stressful. If you are a developer and your hands are fine right now, try it anyway. Treat it as future-proofing."

It does not have to be all or nothing

"I do not code entirely by voice. I probably never will. But I do not need to. Shifting 70 percent of my input to voice was enough to let my hands recover. The keyboard is still there when I need precision. The key is balance, not elimination."

Your career is not your typing speed

"I used to take pride in my typing speed. Now I take pride in my problem-solving. The code I write has not changed. The way I input it has. And honestly, nobody at work noticed the difference except to comment that my docs got better."

Resources for Developers with RSI

If Alex's story resonates with you, here are some starting points:

• Carpal Tunnel Syndrome: A Developer's Complete Guide — Detailed information about CTS, prevention, and treatment
• RSI and Voice Typing: How Dictation Can Save Your Career — Practical transition plan for voice typing
• The Complete Guide to Hands-Free Computing — Full overview of hands-free tools
• r/RSI on Reddit — Active community of people managing repetitive strain
• Talon Community Slack — Thousands of developers using voice-controlled computing

Important: RSI is a medical condition that requires professional treatment. Voice typing and ergonomic changes complement medical care — they do not replace it. If you are experiencing pain, numbness, or tingling, please see a healthcare professional.

There Is a Path Forward

Alex's story is not unique. Thousands of developers have navigated RSI and found ways to continue doing the work they love. The tools exist. The community exists. The path is real.

If you are in the early stages of RSI, you have an advantage: time. Start making changes now, before the condition forces your hand. Try an ergonomic keyboard. Set break timers. Download Murmur and start voice-typing your Slack messages.

If you are further along — dealing with real pain, considering career changes, wondering if you can keep going — know this: developers who take voice typing seriously and commit to the transition overwhelmingly report positive outcomes. It takes effort, patience, and a willingness to work differently. But it works.

Your hands may have limits. Your career does not have to.