This is part 22 of 30 in the Hammertime Sequence. Click here for the intro.
At some point around the end of high school, being fast became unfashionable. When did this happen?
Why do we channel so much more energy into doing more difficult things, instead of doing simple things faster? How much faster could you do your job? Two times faster? Five times?
Instead of I want to be stronger, say I want to be faster.
If you pay attention to speed, you might just find a way to do a whole week’s worth of work in five minutes.
Day 22: Speed
Here are three exercises to help you find that rush of mind working on overdrive:
- Typeracer. Play this game for five minutes. How much faster did you get at typing? What did you learn?
- Go on YouTube and watch a talk at 2x speed for five minutes. If you’re having trouble following, turn on subtitles. Notice that this is possible.
- The Arithmetic Game. Play three rounds of this with standard settings. How much faster did you get?
Here are three principles I’ve extracted from using Yoda Timers to do everything faster.
1. Mistakes Are Fatal
When I first played Typeracer, I started out at a measly 70 wpm and worked my way up to around 90 by just trying harder. Eventually, I hit a plateau because I was still constantly making typos and backspacing. Each mistake cost the time of four or five characters. The backspace key was my Achilles heel.
That’s why I forced myself to slow down and get everything right the first time. At first, this lowered my wpm, but with a bit of work, my fingers felt more nimble and intentional. I cut down the number of typos I made by a factor of 4 or so – it turns out there’s a handful of sequences of keys I constantly get wrong or out of order. My wpm skyrocketed to 120.
In real life, mistakes are even costlier. Getting sick is way costlier than having good hygiene. In programming, it’s common knowledge that testing and bug-fixing takes at least three times as long as writing code in the first place. In math, months of paper-writing can go down the drain when you finally notice a severe and unfix-able logical misstep. At the Olympics, every single mistake will cost you the medal.
If you want to be faster, you must have zero tolerance for even the slightest errors, and slowing down (at first) to practice perfectionism will be worth it. Get it right the first time.
2. Speed Limits are in the Mind
Everyone has a rough idea of how long things have to take. Solving a hard research problem always takes at least a month, right? Writing a paper should take at least an hour, right?
When I first started playing the Arithmetic Game for middle school MathCounts training, my high score was close to 20. After a few months of dedicated training, my record hit 90, making it onto the leader-board of the time.
For any given task, do not assume you’re doing it anywhere close to your real speed limit. It used to take me at least four hours to write a blog post this length. This one clocks out in just under forty minutes.
3. Speed is Easier than Strength
In intellectual work, it’s much much easier to get twice as fast than twice as good. It’s much easier to multiply twice as quickly than to learn to solve harder problems. It’s much easier to type twice as much content than to write twice as well.
Human beings are supremely good at training rote tasks to maximum efficiency. Take advantage of that. Learn to read twice as fast, write twice as fast, talk twice as fast, walk twice as fast, watch videos twice as fast. I’ve been watching videos at 2x speed for as long as I can remember, and I can’t even tolerate regular speed anymore. Once you habituate to going faster, you reap all this free energy that was just lying around while you were waiting.
Speed is underrated. Short training sessions focused on speed will create lasting impacts on your productivity.
Share your proudest speed record. Fast is fashionable again!
I like this.
Some miscellaneous ones, not in order of proudness, but I'm just curious how many examples I can produce.
Video Speed Controller is much better than the jank chrome extension I was using, thanks! Anime might just be barely watchable at 3x.
I've sometimes found it helpful to subvocalize the word "go" as often as possible.
I feel like I don't fit in really well into existing comments with personal records on speed, since my numbers in these categories are not impressive at all.
I've practiced touch typing, and fairly happy with ~60-70 wpm, though further practice with special symbols would work wonders. I've started using vim (emacs evil mode) several months ago and now know $^@! and numbers much better.
If I am to dig around for something that could be impressive and somewhat related to speed - I've done a *lot* of regular meditation practice over the years and I can see that nowadays I notice distractions much more quickly, often during first second, before the mind had the chance to run away with them from my predetermined point of attention.
Interestingly enough, five minutes wasn't enough for me to get any improvement in typeracer or the arithmetic game. I started at 80 WPM and got results both above and below that on my subsequent tries. Similarly I got 20 on my first attempt at the arithmetic game, 23 on the second attempt, and 17 on the third. I don't think that makes speed impossible to train, it just suggests that it'll take longer than 5 minutes!
Here are some of my proudest speed records:
I'm pretty bad at doing things quickly, but I think my roadblocks are less mechanical skill and more anxiety, executive function, and most of all perfectionism. I know you mention perfectionism as useful for increasing speed, and I think for mechanical skills that's true, but in a lot of tasks I am hugely slowed down at decision points (which are many) by a felt need to make the best possible decision every time, even when the decisions are fairly trivial and/or multiple paths forward are valid and/or perfection is not actually helpful. In this sense I most need to cut down on perfectionism for increasing speed.
Timers are indeed a useful tool for this, though. If I decide beforehand that it's more important to do the task quickly than to do it perfectly, having a timer helps me satisfice more readily (usually a good thing for me, given my baseline) because I'm more aware of how much time I'm spending.
Then, of course, I just need to decide wisely when speed is more important than making good decisions and when it isn't...
My scores on the challenges here:
Typeracer: 113, 108, 111, 101
(I'd done this before - not for training, just for fun. I expect my speed is pretty good largely because of piano. I do wonder how fast it might get if I trained for speed on purpose - though I am not sure it would actually matter very much to my life?)
Arithmetic game: 12, 7, 16, 5
(this depends primarily on how many division problems there are especially how many times I need to divide by 7. I realized I don't actually remember any actual methods for division, so all I can do is decompose the dividend into more easily divisible numbers somehow. I guess it would plausibly be useful for me to relearn how to actually do division, though it doesn't actually come up often.)
I don't think there are any things that I'm very fast at, so nothing to share for the daily challenge.
It's been a long time since I thought along those lines, but it makes a lot of sense, thanks for writing this.
(If I really want to be my usual grudging self, I must add I think you probably gain very little from fast typing - thinking is by far the bottleneck and you can think as you type.)
Calibration exercise: what do you think the average typing speed is?
Rest of comment is in rot13: Vg'f nobhg sbegl jcz. V zragvbarq nobir gung V glcr nobhg n uhaqerq naq svsgl jcz; gung znxrf n uhtr qvssrerapr gb ubj yvxryl V nz gb glcr va trareny. Vg gerzraqbhfyl ybjref gur znetvany pbfg bs zr glcvat Snprobbx fgnghfrf, YJ pbzzragf, rgp. V nyfb guvax dhvgr dhvpxyl naq V orarsvg n ybg sebz orvat noyr gb glcr nyzbfg nf dhvpxyl nf V guvax, r.t. jura glcvat sbe gur checbfrf bs guvaxvat gb zlfrys va Jbexsybjl. Glcvat ng sbegl jcz jbhyq nofbyhgryl pevccyr zr.
I guessed 35 based on typing a bit on type-racer to get a feel of the speed. I seem to be able to sustain 90, although on the long run you'd have to see how mistakes affect that average. I get your point but for me, writing is fast spurts of writing punctuated by long thinking pauses. In my comments and status, I probably spend 10x ballpark more time thinking than typing. It's even worse for some blog post and waay worse for academic articles (only for the first rough draft, not factoring editing).
That's fair. I'd like to avoid typical minding here, though; my experience is that I have way more thoughts than I have time to write them up (both cached and on the fly), so even at my typing speed I still find that typing speed is my bottleneck.