Michael J. Dillon

This got stuck in my head today at work. And now it’s your turn.

Once upon a time, many moons ago (if you look at the header, January), I was trying to flirt with a girl who worked at pageaday.com doing email support.

At this point in the year, namely the first week, anyone who bought a page-a-day calendar who didn’t have the technical ability to operate a toaster ran into a wee bit of difficulty getting the online component of their calendar to work.

The problems were normally password resets, or very simple, very mundane issues. Hundreds and hundreds of the same boring problems.

So I decided to liven things up a bit.

Dear Page-A-Day,

   At the beginning of this week, I noticed that my Page-A-Day "365 Days of
Duct Tape 2007" calendar had run out of pages. Since I purchased this on
February 16th of 2007, I was only able to properly enjoy 318 days of
witty adhesive commentary.
   It is marked clearly on the outside packaging that I should expect a full
365 days of duct tape commentary. Who do I need to speak to in order to
access pageaday.com for 47 days in 2008 so that I may actually enjoy all
of the tips, tricks, and jokes to which I am entitled?
   I am a very reasonable man, and I am willing to accept the fact that I
waited 3 days to bring this sticky situation to your attention. I don’t
feel that these days need to be replaced, merely the entire situation
patched.

Thank You,
Mike Dillon

Now. I dutifully waited for this girl to send me a message noticing my attempt at humor. This was not to happen. Instead I received the following reply:

Please call Rachael @ 1-800-722-7202 in customer service.  Thank you.

Which would have been all well and good, however Rachel was the wrong girl.

Obviously I didn’t want to actually make that call, but I did have the deep desire to turn the insane in my reply all the way up to 11. There was only one way to answer:

Dear Rachel,

   Unfortunately, I enhanced my phone with a duct tape shell in mid April
of last year. The doctors say that if I am attached to the idea of growing
hair on the side of my head, I need to discontinue my use of it. I hope
you understand that I am unable to call you because of this.
   In a fortuitous coincidence, I recently discovered that my neighbor
purchased this year's calendar after bonding with some of my creations
over the last few months. He has promised to slip me the day-old pages as
the year unrolls.
   In my eyes, all is well. I hope you have a Happy New Year.

All the best,
Mike Dillon

I’ve been trying to toy with the QuantLib library for the last few weeks, but didn’t get a chance to do it seriously until very recently. I would put an object together, call a few functions, that kind of stuff. I never got quite to the point where anything worked enough to check the output of anything. I actually spent more time putting together a database of all the outstanding Treasury obligations than I did toying with the actual functionality of that library.

That’s largely because at each step along the way I ran into issues. Getting QuantLib set up meant that I needed to get the Boost library working properly. Getting the new version of Boost working properly meant that I actually had to understand what was going on in Cygwin. Cygwin being the UNIX-in-Windows-environment that I’m using as my development platform.

It’s like an onion. You want to do one little thing, and you spend three times as long just getting ready to start.

As for that database, I do know just how boring that sounds. But that was just a quantifiable set of data that I could use to test that my instillation of MySQL was working properly. You know, after I got MySQL server installed on my 5 year old laptop, figured out how to used the gui administration tools, defined a database, designed the table to put the data into and spent an hour on the TreasuryDirect site downloading the list of active securities.

The part I haven’t mentioned is that in order to access the MySQL data in my C++ programs, I need the MySQL C library built, and then need to get the MySQL++ wrapper library working on top of it. Which is does. Now. Finally.

So long story short, I’ve been a bit of a computer nerd in the last few weeks. At one point I thought this would take me a day, two at most. This was in early April. I really just finished last Friday.

Ah well. The data is here, my programming environment is ready, and I actually have the first example program working.

That’ll be my next post.

I actually got an IM asking why I bothered to post a link to the red dot page, when it was just a dot on a page.

Well, you can drag it around… thats what makes it interesting…

Click here. Total amazingness.
(this was me playing with a simple CSS stylesheet and some Javascript.

The basic idea here is to dust off my old CS skillset, and add a bit to it.

Now what does that mean?

Once upon a time, in elementary school, I discovered the BASIC language. Middle school it was C, x86 assembly and I began to poke around the wilds that are the internet. Highschool? C++/Java/VB/etc. at which point I entered college and become a Computer Science major.

Anyway, long story short, once I became gainfully employed at a financal firm, that all stopped. At work, when I was doing anything programatical, it was in Perl. Also, working in finance, my free time went away.

Now, almost three years later, I’ve missed the whole web 2.0 thing, just like I missed the dot-com bit back in the 90’s. The first time it was my due to my age, now its just my fault.

But beyond that, C++ has been my primary language for over a decade, but I’ve managed to miss the Rise Of The Boost Library. Heck, I can barely remember the STL anymore.

But even then? What about things I had never worked with before? Like doing anything with a database beyond quering data, playing with Ruby on Rails, or for that matter blogging.

This isn’t so much a single project, but as it is a collection of things I’m using to learn whatever it is that strikes my fancy.

Mike Dillon (Hi!), a twenty five year old middle office guy who spends his days, and well, some weeknights, working at an asset manager in New York City.

This blog is about what I do when I’m dorking around outside of work.