I Stopped Typing for a Week. Here Is What Happened.

I did not plan to quit typing. I planned to rest my wrists for a few days after a bad flare-up of tendon pain, use voice dictation as a stopgap, and get back to normal by the weekend. Seven days later, I had not gone back. Not because I could not. Because I did not want to.

Day One: Slower, Then Faster

The first morning was uncomfortable. I use VoiceInk to pipe speech directly into whatever app I have open, which removes most of the friction, but I still felt like I was performing rather than writing. Every sentence felt deliberate. I kept stopping mid-thought to correct myself, which defeated the point.

By afternoon something shifted. I stopped trying to dictate clean copy and started just talking. The quality of the first draft did not drop. If anything, the sentences were longer and more complete, because I was not rationing words the way I do when typing.

Day Two and Three: The Email Problem Disappears

Email is where I expected dictation to feel most awkward. Instead it became the clearest win. An email I would have spent eight minutes composing, reading, tweaking, and sending took about ninety seconds to dictate. I said what I meant. I hit send. The recipient got more information, not less, because I was not trimming for typing convenience.

By day three I had stopped thinking of email as a task that required effort. It became more like leaving a voicemail, except the other person gets text.

Day Four: The Hard Part

Code comments nearly broke the experiment. I work with a lot of technical terminology, and my dictation accuracy on things like function names and variable syntax was poor. I ended up dictating the explanation in plain language and then cleaning up the specific terms manually, which added time.

This is a real limitation. Voice dictation in 2024 is excellent for prose and awkward for anything with symbols, camelCase names, or domain-specific jargon. I adapted by dictating the intent, not the implementation, and that turned out to be the more useful comment anyway.

Day Five: Something I Did Not Expect

I started capturing more ideas. Not because I was trying to, but because the barrier to capture had dropped so low that I stopped filtering. Walking between rooms, I would just speak a note. Lying in bed with an idea I would have lost by morning, I said it out loud and it was there when I woke up.

The ideas were not all good. But some of them were, and they would have evaporated under a typing workflow.

Day Six and Seven: The Wrist Question

The original reason for the experiment, my wrist, felt noticeably better by day five. That is not a clinical data point. But the relief was real enough that I started thinking about what a long-term voice-first workflow would actually look like, rather than just getting through the week.

I still used a mouse. I still typed passwords and terminal commands. But my total daily keystrokes dropped by something close to 80 percent, and the hours I normally spend with my wrists in a fixed, loaded position shrank accordingly.

What I Kept After the Week Ended

I went back to typing for code. I kept dictation for everything else: emails, documents, notes, Slack messages, first drafts of anything longer than a paragraph. The split took about two days to feel normal.

The one thing I would tell anyone considering this experiment: do not try to dictate the way you type. Let yourself talk. The clean version comes in the edit. The first version just needs to exist.

Spend a week being less careful with your words, and you might end up with more of them.