From 7c72326946f755d28d6f6ad05ac9b1589b89f4f5 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 25 Aug 2024 23:05:22 +0300 Subject: Update content for gemtext --- gemfeed/2024-08-05-typing-127.1-words-per-minute.gmi | 5 +++-- gemfeed/atom.xml | 7 ++++--- index.gmi | 2 +- uptime-stats.gmi | 2 +- 4 files changed, 9 insertions(+), 7 deletions(-) diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.gmi b/gemfeed/2024-08-05-typing-127.1-words-per-minute.gmi index 5cd6f4a4..b6b848bd 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.gmi +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.gmi @@ -135,11 +135,11 @@ I wrote myself a small Ruby script that would randomly select a paragraph from o Overall, I trained for around 4 months in more than 5,000 sessions. My top speed in a session was 127.1wpm (up from barely 10wpm at the beginning). -=> ./typing-127.1-words-per-minute/all-time-stats.png +=> ./typing-127.1-words-per-minute/all-time-stats.png All time stats My overall average speed over those 5,000 sessions was 80wpm. The average speed over the last week was over 100wpm. The green line represents the wpm average (increasing trend), the purple line represents the number of keys in the practices (not much movement there, as all keys are unlocked), and the red line represents the average typing accuracy. -=> ./typing-127.1-words-per-minute/typing-speed-over-lessons.png +=> ./typing-127.1-words-per-minute/typing-speed-over-lessons.png Typing speed over leson Around the middle, you see a break-in of the wpm average value. This was where I swapped the `p` and `;` keys, but after some retraining, I came back to the previous level and beyond. @@ -150,6 +150,7 @@ These are some tips and tricks I learned along the way to improve my typing spee ### Relax It's easy to get cramped when trying to hit this new wpm mark, but this is just holding you back. Relax and type at a natural pace. Now I also understand why my Katate Sensei back in London kept screaming "RELAAAX" at me during practice.... It didn't help much back then, though, as it is difficult to relax while someone screams at you! + ### Focus on accuracy first This goes with the previous point. Instead of trying to speed through sessions as quickly as possible, slow down and try to type the words correctly—so don't rush it. If you aren't fast yet, the reason is that your brain hasn't trained enough. It will come over time, and you will be faster. diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 624bca81..e77e8244 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2024-08-24T19:58:56+03:00 + 2024-08-25T23:04:41+03:00 foo.zone feed To be in the .zone! @@ -158,11 +158,11 @@
Overall, I trained for around 4 months in more than 5,000 sessions. My top speed in a session was 127.1wpm (up from barely 10wpm at the beginning).

-
+All time stats

My overall average speed over those 5,000 sessions was 80wpm. The average speed over the last week was over 100wpm. The green line represents the wpm average (increasing trend), the purple line represents the number of keys in the practices (not much movement there, as all keys are unlocked), and the red line represents the average typing accuracy.

-
+Typing speed over leson

Around the middle, you see a break-in of the wpm average value. This was where I swapped the p and ; keys, but after some retraining, I came back to the previous level and beyond.

@@ -173,6 +173,7 @@

Relax



It's easy to get cramped when trying to hit this new wpm mark, but this is just holding you back. Relax and type at a natural pace. Now I also understand why my Katate Sensei back in London kept screaming "RELAAAX" at me during practice.... It didn't help much back then, though, as it is difficult to relax while someone screams at you!
+

Focus on accuracy first



This goes with the previous point. Instead of trying to speed through sessions as quickly as possible, slow down and try to type the words correctly—so don't rush it. If you aren't fast yet, the reason is that your brain hasn't trained enough. It will come over time, and you will be faster.
diff --git a/index.gmi b/index.gmi index 27d484e4..ea6128cd 100644 --- a/index.gmi +++ b/index.gmi @@ -1,6 +1,6 @@ # foo.zone -> This site was generated at 2024-08-24T19:58:56+03:00 by `Gemtexter` +> This site was generated at 2024-08-25T23:04:41+03:00 by `Gemtexter` ``` |\---/| diff --git a/uptime-stats.gmi b/uptime-stats.gmi index faf36193..e7fdc739 100644 --- a/uptime-stats.gmi +++ b/uptime-stats.gmi @@ -1,6 +1,6 @@ # My machine uptime stats -> This site was last updated at 2024-08-24T19:58:56+03:00 +> This site was last updated at 2024-08-25T23:04:41+03:00 The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine. -- cgit v1.2.3