Feature request: Increase frequency of characters that are frequently missed

[burbilog]

Three decades ago, I spent a significant amount of time and effort to learn touch typing. About ten years ago, my wife also learned touch typing, but she did it much faster thanks to an interesting keyboard training tool called VerseQ.

VerseQ doesn't use repetitive exercises with hundreds of lines, instead it measures the frequency of failed characters and offers them more frequently than others. For example, it displays a line to repeat, then it presents a line consisting mostly of failed characters.

I also used VerseQ to improve my touch typing at that time, because it was easy to learn all these #!@s that I had never bothered to learn 30 years ago.

I believe this same approach could benefit this game - offer failed characters more frequently than successful ones. The more errors, the more frequency. The better characters, the better response speed - less frequency. I think this method would greatly reduce the time needed for training.

[shervinemami]

Hi @burbilog , that's an interesting idea, but I don't think I'll go to the effort of implementing it. My main intention for this game / tool is for 2 things:

1. Find clashes in an alphabet mapping when 2 symbols are said back-to-back quickly. Gradually, you can tune your mapping to have less clashes until you're happy with your alphabet & symbol & number mapping. This is better to have a uniformly random sequence, in my opinion, which is how the tool currently behaves.
2. Practice over & over again to say the eventual mapping you've decided on. This part might actually work better when behaving like you mention. But it would take away some of the effectiveness of continuing to find clashes (goal 1).

[burbilog]

Hi @burbilog , that's an interesting idea, but I don't think I'll go to the effort of implementing it. My main intention for this game / tool is for 2 things:

1. Find clashes in an alphabet mapping when 2 symbols are said back-to-back quickly. Gradually, you can tune your mapping to have less clashes until you're happy with your alphabet & symbol & number mapping. This is better to have a uniformly random sequence, in my opinion, which is how the tool currently behaves.

2. Practice over & over again to say the eventual mapping you've decided on. This part might actually work better when behaving like you mention. But it would take away some of the effectiveness of continuing to find clashes (goal 1).

I made a patch for this mode, will you accept pull request?

[shervinemami]

Oh nice! Yeah submit a PR and I'll add it 😁