The last week or so has been pretty interesting (see this reddit post for some details). The first few days showed how bad assumptions can quickly become blockers and then how other assumptions can manifest themselves in more subtle ways.
I talked about the first blocker in the previous post but this is more about the latter. I had assumed that the Dexcom’s internal time was standard. That is, I assumed that two receivers would have different display times but the same system time at any given point in time. That proved to be a bad assumption to make. ChickenBeard again helped with this bug by testing my numerous builds and being patient with my varied attemps at finding a more robust solution.
I’m happy to say that it looks like my new approach is now working. The bad news is that previously uploaded data is bad and locally stored archives of your data (a copy that Glukloader keeps for you and for resending data in case of disasters) is also faulty (potentially). The result is bad times (it looks like bad timezone handling). It’s not necessarily dramatic but I’d like to sanitize the data at some point. More to come as I think about this and talk to a few more of you to understand the impact.
Since Glukloader has proven to be very important to the whole interaction with Glukit, I decided to follow edwhittle’s suggestion and add some user feedback with it.
Here’s the link to the new build with both of those: Glukloader 1.0-rc20.
Again, talk to me if there’s anything on your mind.