
The reason for the haste, and for being unable to record this fact earlier, was that somebody - not me - had messed up the meetings and only left us thirty minutes for lunch

And I was very busy the rest of the day as I brought my code into contact with real data, where it immediately encountered an anomaly it hadn’t seen before and did strange things. It turned out this was a known issue with some legacy data from last year, but the developer who knew about it has left and it hadn’t occurred to anybody else to mention it, if they’d even remembered. Anyway, I quickly worked out a way of dealing with it, and got that done this afternoon







Leave a comment: