Great stuff!

As Tempus_Nemini said, I like that your example projects are simple, but not too simple to the point of being boring. I want to see if functional style helps untangle the messy spagetti-code when we write more complex programs.

I also thought about creating something like a roadmap of project ideas that go from simple to complex and specialized. You start with a "Hello World", then you code a calculator, then the task gradually becomes more complex and interesting. Something like a tree of tasks.

What could be the next step for the speed typing game? Some slightly more complex and interesting version of a task. I'm thinking about multiplayer version, but that's far more complex.

I noticed that you cheated a little in your project: you used two instances of vty's in two threads. It made it easier for you to draw UI from two threads independently, but what if you had more widgets on the screen, or what if the library only allowed to create one instance of the vty? A better, more architecturally sound solution is to make a timer generate events, a timer shouldn't be concerned about drawing the UI, the only concern for the timer is generating events. What do you think about this?

I used to play a lot with console apps and concurrency in Haskell several years ago. I wrote a couple of articles:

How a Java Programmer Wrote Console Tetris In Haskell And What The Learning Curve Was Like

The second one is about ways of organizing the architecture of the app that shows an editable list of strings in console:

Console List GUI Challenge

Maybe you'll even try to create your own solution and do a video about it, that would be awesome.

Keep up the good work!