When I’m using Google software I get positive surprises. For example, plot a route in Google Maps then start dragging segments of it to spontaneously change the course.
View Larger Map
Microsoft software never surprises me. It is decade-old bloatware. It usually has an implementation of everything.
When I’m using software from small niche hardware companies, I assume it’s going to suck in countless ways.
My longstanding hate-object was Garmin, but now that Google Maps and my iPhone has mooted standalone GPS units, I have the luxury of not even thinking about Garmin any more.
A new enemy has appeared — my CycleOps Powertap. This is a small cycle computer that wirelessly talks to a rear wheel hub that measures my pedaling torque (thus wattage). Wattage is the most useful telemetry for a bicyclist.
The PowerAgent software that talks to it is shabby and brittle. But of course, that was a known known. I discovered a real gem in the cycle computer’s firmware yesterday. During a long ride, my cycle computer would periodically blink “full.” I had not cleared out old ride data for a while, so the telemetry was filling up. Didn’t really matter, I had already downloaded the old ride telemetry, so having the cycle computer replace it with the new, current ride data would be fine.
Except it didn’t.
Against all odds, the firmware designers decided that it made more sense to simply cease recording new data rather than overwrite the old data!
Why would the default assumption ever be that I value old data more than data I’m currently generating?
Does the cycle computer remember that I downloaded previously? Isn’t that a clue?
If they agree that it really should replace the old data, but were unable to implement that, then they’re just really pathetic.
Entries (RSS)