M2M Day 72: I’m not getting any faster (and four theories as to why)
This post is part of Month to Master, a 12-month accelerated learning project. For January, my goal is to solve a Rubik’s Cube in under 20 seconds.
Over the past 11 days, I’ve solved the Rubik’s Cube probably 400–500 times, which is a lot. In addition, I’ve also focused on learning new algorithms, and training my pattern recognition abilities with a few different exercises.
Ever after all of this practice so far, I still don’t seem to be getting much faster. In fact, some of the speed gains I saw in the first few days seem to be reverting (i.e. I’m going slower than I did ~4 days ago).
I have four theories why this is happening:
1. My cube is getting worse at the same rate I’m getting better
As I practice more and more with my Rubik’s Cube, it’s out-of-the-box buttery smoothness is breaking down. I think this is from a combination of dust and general wear and tear. In other words, the cube is getting harder to turn and sometimes locks up when I’m going really fast.
It’s possible that, as my cube gets slower, I’m getting generally faster, so the effects cancel out and I’m left with an unchanging time.
The potential solution: Lube.
Yes, Rubik’s Cube lube is a real thing and very popular amongst speed cubers. I’ve ordered some on Amazon and will put it to use once it shows up.
2. My brain is getting overloaded
Two months ago, when I was trying to learn how to memorize a deck of cards in less than two minutes, between days 7–10, I dipped to my worst level of performance. My brain had been subjected to so much new information over the previous week, and hadn’t yet caught up. Once it did, after a few days, I made a big leap forward in my progress.
It’s possible I’m experiencing a similar phenomenon now.
The potential solution: Don’t get discouraged and push through. If I don’t see positive changes in a few days, I should reassess this theory.
3. I’m practicing poorly
I’ve noticed that, during real solves, I ignore a lot of the techniques I’ve been practicing. For example, I’ve been working hard to reduce my cube rotations and improve my look-ahead via two main directed exercises. But, when it’s time to apply these principles to an actual solve, I freak out, forget everything, and spin the cube frantically. This is clearly not good.
The potential solution: Combine my training exercises with actual solves, forcing myself to actively look-ahead and keep the cube positionally controlled.
4. Poor pre-solve planning
Before every solve, speed cubers are allowed 15 seconds to inspect the scrambled cube. During this time, it’s advised to make some sort of plan.
Typically, most speed cubers can plan out the entire cross and one F2L pair during inspection. On the other hand, I seem to only plan, on average, two of the four edge pieces necessary to form the cross.
As a result, my cross is still too slow, and my transition to F2L is usually terrible. After I finish the cross, I pause for maybe 1–2 seconds just to assess the situation.
This is not good.
The potential solution: Practice planning out the full cross during inspection. Also, practice tracking an F2L pair while executing the cross, so I can smoothly transition from the cross to F2L.
(Not sure what “the cross” or “F2L” are? Read my post about how I solve the Rubik’s Cube)
Validating these theories
When learning new skills, especially for speed, it’s always a good practice to form hypotheses about where the major inefficiencies lie, and then attempt to validate/invalidate these theories.
That’s what I plan to do over the next few days, which will educate my training moving forward.
Read the next post. Read the previous post.
