It took me a full 10 minutes to track down this stupid bug. It is not intuitive. I guess it is the penalty one pays for terseness:

vCostEntry.getCost().put(vDBField, Utils.makeProperString(vExportToExcel).equals("DISCOUNT")?((int)Utils.getDouble(vRawAmount)):GetIntFromFormattedCurrency(vRawAmount));

Some definitions to explain above:

This is official. The past 365 days I have spent in Canada mark both the coldest weather I have ever experienced at -35C (this was a few days after the screenshot I took below) with windchill at -42C:

to the past week's temperatures of 38C (humidity index of 43C):

I have been struggling on and off with EasyFrom DBConvert converting a Paradox 4 database to MySQL. I would get this error intermittently:

[800A0CB3] Object or provider is not capable of performing requested operation.

The weird thing is I'll work just fine the one day, then the next I get that error. So I finally tracked it down - two main causes. The first is the Collation scheme - my paradox files uses International scheme, for some reason sometimes my system default gets reset to ASCII.

This must have been one of the most special photography excurions I had been on, ever. It started with us driving to Stanly Park to park our car, since we knew Sunset Beach would be a no-go for finding parking since everyone would be at the Celebration of Light show where South Africa showed their best work.

Once there, we had to walk about 4km to Sunset Beach to claim our spot. This was 17:00. It started out to be an awesome evening, but after an hour it started dripping on / off. Determined to see this through (the show only started at 22:00), and with no real protection from the rain we waited it out. My wife and I were soaked already at 18:00. Fortunately my daughter hid away in her rain coat.

Then it started - thunder and lighting, quite unusual for Vancouver. The lightning danced around us whilst the west got more and more orange. At some point all realism was lost. Here is what I mean - with rain pouring down on me I took this photo:

I recently uncovered a bug that troubled me for about 30 minutes. This bug was introduced in the Javaconfig framework, as I was extending support for more overloaded methods by "copying the pattern". But it proved that in this case, following a pattern does not always work.

Inductive reasoning states that if element 1 is the same as 2 and 3 and 4 and ... n, element n+1 will most probably be the same as well. However inductive reasoning is rather evil when writing software as it is not mathematically sound.

Here is the code - spot the problem: