Reposted here from Facebook for reference: Not sure how many out there are Fitbiters but I believe this applies equally to all wrist/LED-based HR monitors (e.g. Apple Watch, Garmin devices, and other trackers). My own anecdotal testing corroborates this study as does DC Rainmaker’s review of the Garmin 235, i.e. they are good at low […]
I’ve been meaning to write out this for a while but this past week finally spurred me into action. It’s been a trying week for some if not all (tri)athletes out there, well, the ones that use a Garmin device, which is just about all of them. Actually, now that I think about it, I
I love Strava! However, as with all tracking sites, Strava doesn’t always provide the exact window I want into my data. I’ve been thinking about building an app that allows me to manipulate the specific data I’m interested in but to do that, one has to get the data first. Given that, I’ve been playing
The Silicon Valley Triathlon Club (SVTC) used to have an old Perl based VDOT calculator. If you don’t know what VDOT is, take a look here or at Jack Daniel’s wiki page. The SVTC calculator has not worked for a long time, so I managed to get the code behind the calculator and rewrote its
Virtually every triathlete I know owns a Garmin product of some kind and I’m no exception. I’ve been using Garmin hardware products for over 5 years now and am continually disappointed with several aspects of the experience. Here’s my latest issue. It’s probably not a big deal but if you have a Garmin USB stick