Wednesday my hands were very sore tried dictation to write my code then I put my hands on break.
No seriously, that sucked.
You can see the full video here 👇 took me 30 minutes to write 8 lines of code, a React adder component.
Move left, move left, move left, move left, delete that, delete that, move left, function, undo, undo, delete that, move left, move left, undo, agh damn it why did you write that, crap, undo, undo, undo, ok, no wait, uaaaaa
I learned that I curse under my breath when things go wrong. When your computer is listening and types out everything you say ... 😅
With MacOS Dictation you press command twice and off you go in voice control mode. Anything you say, the computer tries to translate into written text.
So easy to forget to turn it off. Especially when you mumble or you mispronounce something, the computer gets confused and goes down a weird rabbit hole.
You then have to stop dictation and reset from scratch. This happens a lot.
Dictating text worked well. Code and voice commands ... urgh.
MacOS Advanced Dictation gives you a bunch of special commands. Like move left, delete that, capitalize that, move to end of word, etc.
All great in theory, but half the time my computer would type out the command instead of doing the thing. Replacing uppercase letters with lowercase was a constant chore.
Say you want to write
function, here's how you do it 👇
🗣 *function*Function |🗣 *move left*Functio|n🗣 *move left*Functi|on🗣 *move left*Funct|ion🗣 *move left*Func|tion🗣 *move left*Fun|ction🗣 *move left*Fu|nction🗣 *move left*F|unction🗣 *delete that*|unction🗣 *lowercase f*f|unction
Imagine your hands break down and that's your life for a few weeks or months? Oof.
You'd get better at it, find other software than built-in dictation, but still ... we take our keyboards and impressive typing speeds for granted don't we?
Gotta be careful with that.
Keyboards will wreck your hands. That warning label on the back saying "Prolonged use of this device can cause serious injury" is not joking around.
If voice works so well for Alexa and dictating text messages, why not for writing code?
It's all got to do with how speech recognition works.
Speech recognition is a tough fuzzy computational problem. Everything from signals processing to machine learning has to work just right.
In a nutshell (because I'm no expert) 👇
- Listen to a microphone
- Find the human voice
- Filter out noise
- Filter out irrelevant background humans
- Tokenize human voice into words (this is based on trained machine learning models using many different dialects and accents)
- Decide how well you recognized individual words
- Feed certainty weighted words into a statistical model, often a hidden markov model (more trained machine learning models)
- Use statistics to fill in the blanks
- Try a few options to get the likeliest sequence
- Turn result back into text
Lots of fuzziness and statistics. Each step of the way, something can go wrong. And it does.
Computer can misunderstand a word, mishear something, you might pronounce it weird, or there might just be too much noise. Computer fills in the blanks with an educated guess.
Sometimes as you keep talking, you change the meaning and the computer realizes it made a mistake. Goes back to fix the word so it makes more sense.
You can see this working beautifully when dictating text messages. It's gotten so good I prefer to dictate my texts when I'm on the go. Much easier than the iOS keyboard 😇
You do this all the time inside your brain.
Ever noticed how it's easier to understand a good friend at a noisy bar than it is a stranger? Or how difficult bar conversation becomes when you're with non-native speakers?
That's because you're better at guessing what your friend says than a stranger. And your foreign friends have accents that are harder to filter out from the noise so there's more guessing.
Or vice-versa if you're the foreigner.
Very hard to chat in a loud bar coz you can't follow what's going on. Or at least I can't ...
With deep learning and big data, speech recognition has become really good for prose. Amazing even. If I didn't type at 120wpm on my keyboard, I'd be dictating this article right now.
I already speak into my phone, for texting, almost as often as I type. It's easier.
So why not code?
It's all got to do with steps 7 and 8 in our list. You are speaking in symbols and indentation and weird words in weird sequences.
🗣 *use state*
What is that? Is it
Use state or
useState? How is a computer supposed to know?
Based on all its data, all the training sets,
Use state is its best bet. You are likely starting a new sentence. It's a weird sentence, but the computer don't judge.
useState, the computer would have to understand your code. It would need to know you are writing a React Hook, not just a code comment.
You get the picture 👉 you need a new trained statistical model for every language you want to dictate.
Works great for English. Might take a while for all these weirdo esoteric programming languages we like to use. I wouldn't hold my breath 😅
So what can you do to avoid this right now?
Invest in a good keyboard, get a good mouse, learn how to relax your hands, type without moving or bending your wrists too much. Do it now before it's too late.
You won't like coding with your voice.
PS: before you ask, I like the Truly Ergonomic keyboard and a good Logitech mouse. Apple has the worst least ergonomic input devices. Make sure your forearms are at a comfortable angle to your keyboard, do not try to keep them perpendicular. Yes even on a laptop keyboard. Plop your mouse hand on the mouse like a dead fish. Do not grab. Try to move with your forearm, not your wrist or fingers.
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️