QuickFIX buns

Writing applications with QuickFIX has some fun. The FIX engine there is a classical IoC, event driven. Application that uses it has to have only business specific things don't bother with tedious FIX noodles. Easy peeasy.

However, sometimes I have had anxiety because that specifics were not covered properly by tests. No, I tried, tried hard really. With mock or without it, tests for application with QuickFIX looks ugly and non readable due its restrictive and cumbersome design. Very often I had to remove them or simplify their verification because clearly understood that after couple months even I will not be able support it.

Eventually I came to an idea to simplify all that. QuickFIX users may appreciate this. :)

Co - (r)relation?

Sometimes there are interesting things happen in a life. Interesting in a perspective of unexpected correlation. Or rather pretending to. Second time I fall back to Javascript , and second time in transition to a new job. What would it mean? :)

Anyway, here is just a modest announcement about the new reincarnation of an old syntax highlighter. Now it is all as it should be: project in SCM and so on... Ok, almost as it should be.

TomorrowOn Monday will check it on IE at work. WebKit it seems like works.

FIX logs or why I love AWK

Some time of past year I spent in attempts to convince people did not rely on FIX logs especially if they collected from different JVMs or even hosts, in their attempts to measure latency on FIX message exchange. That may sounds silly, but finally I gave up and made some scripts that helps to automate process. Unexpectedly (for people, not for me) results were controversial and unpredictable. But this post is not about this. I decided pay tribute to a wonderful utility without which I just can't imagine how would I cope with that task. Let me write some warm words about AWK. It really outstanding one beside other data driven script engines due its power and flexibility.