Touch Typing Week #1

Well, I must say that it is harder than expected and also I was too lazy to do it every day at least not for 30 minutes (on average I was touch-typing for 21 minutes a day). Anyway there is some progress, see the chart below (don’t pay much attention to the first 2 days – I was not positioning my hands correctly for doing proper touch typing, on the 3rd day that was fixed and speed dropped almost below zero 🙂 along with the number of typos). So now I am able to touch-type 12 words per minute doing 10 errors, that’s it for the first week.


FPLog Begins

In my previous post on logging I wrote about how it could be future-proofed and now I would like to give this concept some development.. literally – I want to develop a logging solution based on the concept presented earlier.

The solution will consist of client and server parts.

  • C++ and Java API
  • Various transports (Ethernet, Bluetooth, Serial, USB)
  • Windows, Linux and Android support


  • MongoDB as persistent storage
  • GUI application in Java and Spring
  • Windows and Linux support

With this project I would like to practice multiplatform development, refresh my rusty Java in the process and finally create a logging solution that I can use later in some other projects. Well, let’s see how it goes, hopefully not like 99.999% of such hobby side projects (hint: dev/null 🙂 )

By the way the name of the project is ‘fplog’ which reflects the idea of this solution being future-proof.

Future-proof Logging

Some time ago I had a project that required working with lots of exchange orders, these orders were arriving into the system in hundreds per second: some were filled, others modified or canceled. In other words there was always some processing involved that needed to leave some traces in order to understand what happened with the particular order in case of some client dispute.

Project was developed from scratch therefore it was my decision on how to introduce logging there. As the feature seemed low priority not much time was invested in it and as a result a simple unstructured text logging with timestamp & priority was implemented. It was very human-readable and seemed pretty good until the project went public…

Every week I got a few gigabytes of text logs to process in order to find this or that problem or just to make sure the system is functioning as designed and everything is fine. During that time there were couple of severe problems detected very late because of this very inconvenient and time-consuming process.
After thinking over this mess several things became clear: text files are very inconvenient logs storage and a Nagios probe (or some other automated solution) should be reading the log in my place.

Logging mechanism improvements were in order: introduce some structure to log messages (make some mandatory and optional parameters that every log message has) and use database for logs storage.
After implementing these improvements we could easily search DB for errors ourselves or setup some Nagios probes that regularly do it for us.

To be fair I must confess that I left the company before improved logging mechanism was introduced, it was only half-way there, meaning that only some of the log messages were stored to DB – only those messages that were a consequence of some exception happening in the code and automatic probes could analyze only this portion of log searching the DB for the red flags so to say.

Anyway even this portion of the log stored inside the DB showed that some problems still remained with this approach: SQL database with its fixed schema was too rigid and inflexible storage for the log messages which can have arbitrary number of arbitrary parameters.
The answer is to store the logs into a NoSQL schema-less document database in an easily-parsable form which allows any parameters for a specific message.

I should give a guy who wrote this post a credit for making a case of using JSON as log message format, he also mentions systems that can be used for storing, searching and presenting the logged information.

All of the above makes me think that using the structured logging and storing everything to schema-less DB provides a pretty flexible solution that could withstand a test of time and in particular the everchanging requirements which is the hardest test for any system. Even the syslog protocol has some place for structured log information since RFC 5424 (see 6.3. STRUCTURED-DATA section) although this RFC is still in a proposal state.

Learning Touch Typing

The first skill I would like to master in 2014 is touch typing. I made several attempts previously but failed because the task is too boring and repetitive.. Some say the skill is essential for programmers some disagree and there seem to be no real facts – only opinions. Well, I am going to test it either way because despite the typing speed is not so important while coding, thinking about typing distracts from the code and ideas that you are trying to code.

I intend to train for 30 minutes a day and report the progress. Searching the net for touch type tutors I have found one solution particularly popular in Russian segment of the net, called ErgoSolo. Downloaded, installed, tried, puked, uninstalled. I will not even give you a link to this crapware – wants to install a bunch of Yandex shit together with it and also has a very unfriendly DRM – install only on 1 PC, if there are hardware changes to your PC you need another registration code and if hardware changes occurred after 6 months from purchase you will have to repurchase, no kidding..

Long story short, I am using, so far so good – supports languages I need (English and Russian) and is free for now at least. Currently I am touch-typing like a pro with astonishing speed of 12 words per minute making mere 22 mistakes 😉 Hopefully this situation improves in the coming weeks (target is 5 weeks for both languages, digits, functional and other keys).