RVS_ParseXMLDuration VS typocide

Well, these ones aren't "half-baked," but they are no longer being maintained (archived):

[0] https://github.com/RiftValleySoftware/RVS_IPAddress

[1] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration

[2] https://github.com/RiftValleySoftware/RVS_ONVIF

This project is unfinished (I just walked away from it, as it wasn't really giving me what I wanted):

[3] https://github.com/RiftValleySoftware/RVS_GTDriver

This one is "half-baked," I believe. I never really took it particularly far:

[4] https://github.com/RiftValleySoftware/RVS_MediaServer

Not completely. The way that it works for me, is that I start work on a project, and, while building, I notice that some code that I'm working on is:

1) Pretty complex, and fairly insular; and/or

2) Possibly useful, elsewhere.

If that's the case, I will then stop work on the main project, and take some time to extract and "genericize" the subproject. I'll usually set it up as a standalone open-source project; complete with tests and documentation.

This may happen before I have completed the coding in the main project, or may happen as the result of a review, after the fact.

In some cases, I very clearly need to develop a subproject before starting on the main project, or before certain milestones within that project (for example, SDKs or drivers). In that case, the timelines are completely separate.

If you look at my GH repos, you'll see a whole bunch of these projects, including some rather strange ones, like an XML duration parser[0]. These are the types of projects that I extract.

In some cases, I end up not using the extracted project in my main project (happens to some of my UI widgets). In that case, even though I am not using it, I still have an excellent project for the future. Here's an example[1]. I have ended up not using the spinner in my own work, as it was too obtrusive a widget, but it's nice to have it available for future projects.

[0] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration

[1] https://github.com/RiftValleySoftware/RVS_Spinner

- Typocide - https://github.com/rdavison/typocide

Typocide is a CLI based typing tutor. It solves a few problems which other typing tutors failed to provide for me. In particular it uses real world text instead of fake text such as keybr. The corpus is derived from all the quotes available on Typeracer.

Next, it draws inspiration from leveltype (https://github.com/christoofar/leveltype) which bans the use of the backspace key. If you make a typo, Typocide will create a practice test where the typo'd word is the focus. It will then build a test which includes not only the surrounding words for the current test (previous and next word), but also the surrounding words from previous tests where you have typo'd the word.

The idea is that when you make a typo, the word was a part of some context, and rather than simply practicing the word, you want to practice the word in context. A lot of typos, particularly in speedtyping happen at word boundaries. Furthermore, by having it operate on context, it also reinforces common idioms. For example, the word "example" is very likely to be preceded by the word "for" and very unlikely to be preceded by a word like "kaleidoscope". So it makes sense to practice "For example," as a unit.

Furthermore, it has some rudimentary support for identifying words which you have typed more slowly than usual. Typocide will also generate practice tests from these slow words.

Sometimes the tests are not perfect, so I have added a simple escape hatch: if you press TAB on a new test, it will skip the test, and if you press TAB after you have started typing a test, it will repeat the test from the beginning.

This project is half baked for two reasons: