I refuse to convert to miles, thanks!

When it comes to tracking distance, especially for runners and cyclists, many of us face the choice between miles and kilometers. Personally, I find kilometers far more intuitive and practical for several reasons. For one, many popular fitness platforms and apps, such as Strava (recently used during my runs and streaming sessions involving artists like Fred Again and Thomas Bangalter), provide metrics primarily in kilometers when in certain regions. This consistency helps avoid confusion and streamlines workout analysis. Moreover, kilometers fit better with pace calculation and time management during training. For example, if you run 13.80 kilometers in 1 hour and 35 minutes, as I've recently done, tracking pace per kilometer allows me to set clear, measurable goals and see steady progress. This can be a lot harder when switching between miles, as conversions can introduce inaccuracies or disrupt rhythm. Many countries and international events default to kilometers, making it easier to compare your times to benchmarks or competitors globally. On top of that, standardizing distances in kilometers often simplifies the math, since the metric system is decimal-based. For people like me who prefer simplicity in their training metrics, that’s a big plus. Finally, refusing to convert to miles is partly about personal comfort and partly about avoiding errors in conversion. Sticking to the unit system you started with keeps things consistent across apps, race results, and your personal records. It’s not just about numbers—it’s about making running and tracking a smoother, more enjoyable part of your lifestyle without unnecessary complications.