If you've ever used MonkeyType, you know you can just breeze past mistakes. You hit the wrong key, the word turns red, and you keep going. Your accuracy score takes a hit, but you don't actually have to fix anything. You move on.
I think that's the wrong call. And I built Clackpit differently because of it.
The case against "press on through mistakes"
Here's the thing about typing: it's a motor skill. Your fingers are building muscle memory with every keystroke. When you press the wrong key and keep going, you're not just making a mistake — you're reinforcing it. You're training your hands to accept the wrong movement and then correct course mentally.
That's not how you get faster. That's how you get fast-but-sloppy.
Every professional typing curriculum I've read makes the same point: accuracy first, speed second. Speed is just what happens when accurate movements become automatic. But you can't automate inaccurate movements into accuracy by doing them quickly.
MonkeyType lets you bulldoze through errors because it's optimizing for feel. It feels great to keep typing even when you mess up. You still get a WPM number at the end. The game continues. But that feeling comes at a cost to your actual improvement.
What forced correction actually does
In Clackpit, if you mistype a character, you're stopped. You have to delete back to the error and retype correctly before you can continue. There's no moving forward past a mistake.
When I first implemented this, I thought people might hate it. It's genuinely more frustrating in the short term. Your WPM scores feel lower because your effective speed is lower — you're spending time on recovery, not just forward motion.
But that friction is the point. The frustration is exactly the signal you need.
Forced correction creates a tight feedback loop: wrong key → immediate stop → muscle memory fires again → correct key. That loop, repeated hundreds of times, is how your fingers actually learn. Without the stop, you get a loose feedback loop: wrong key → mental note → keep going → eventually less bad.
The drill loop compounds it
Forced correction in-race is one thing. But Clackpit also tracks which words you stumbled on and offers a one-click drill: after every race, you can pull up just those words — the ones where your fingers fumbled — and run them again, five repetitions each.
This came directly from a thread on r/typing where someone asked for exactly this feature two years ago. Eighteen upvotes and then nothing shipped. I built it because I've wanted it myself for years.
The combination is what makes it work. Forced correction means you fix the error in context. The drill loop means you go back and drill the specific weak spots in isolation. It's the same methodology a piano teacher would use: play the piece correctly, then isolate the hard passage and work it until it's clean.
Where MonkeyType gets it right (because fair is fair)
MonkeyType is genuinely good at what it's trying to be. If you already type accurately and you're trying to push your ceiling, flowing through mistakes and focusing on raw speed makes sense. It's a speed benchmark tool. The experience it optimizes for — fast, fluid, uninterrupted — is the right experience for that goal.
Clackpit is optimizing for something else: improvement. The target user isn't someone benchmarking their ceiling. It's someone who wants to type better than they do now.
Both are valid goals. They just need different tools.
The uncomfortable truth about most typing games
Most typing games optimize for engagement, not improvement. Uninterrupted flow feels good. High WPM numbers feel good. Social leaderboards feel good. None of those things are bad — but they're not the same as actually getting better.
The design decision I keep coming back to is: what does the user actually want at the end of six months? Not what feels good in the next three minutes, but what will they have gotten from using this?
If the answer is "higher WPM and fewer typos in real work," then forced correction isn't a punishment. It's the feature.
If you want to try it: clackpit.launchyard.app — no account required, works in your browser. Brutal feedback welcome.
Top comments (0)