Unpublish the draft
All checks were successful
Build and copy to prod / build-and-copy (push) Successful in 2m7s
All checks were successful
Build and copy to prod / build-and-copy (push) Successful in 2m7s
This commit is contained in:
parent
aab2e16d37
commit
500dc71c90
@ -2,6 +2,7 @@
|
||||
title: An observation on measuring speed vs cadence
|
||||
tags:
|
||||
- cycling
|
||||
- draft
|
||||
date: 2024-04-21T14:30:00.000Z
|
||||
---
|
||||
|
||||
@ -9,12 +10,3 @@ I'm writing this quickly after coming back from an 82km bike ride.
|
||||
|
||||
When I first started cycling, I didn't have a dedicated GPS unit, instead I just recorded my rides using my phone so that I could share them to Strava. I couldn't tell how fast I was going until afterwards, so my speed didn't matter; I was just riding for fun.
|
||||
|
||||
|
||||
* Started cycling, had no GPS unit and just recorded using phone
|
||||
* Speed didn't matter
|
||||
* Had some fast-paced rides last year
|
||||
* GPS unit displays my current speed on the display
|
||||
* Wearing self out to maintain the "correct" speed even when it's not the right thing for me at the time
|
||||
* Actually I'm better off measuring my cadence, heart rate, and power output and keeping those in the correct zones
|
||||
* They'll bring the actual benefits
|
||||
* Tie back to software dev and measuring the right thing
|
||||
|
Loading…
Reference in New Issue
Block a user