Blog

Summer of Cycling Events (2026)

Last year my cycling goal was all about volume: 365+ hours on the bike. It was a fun challenge, but by the end of it I was fairly burned-out from cycling. So for 2026 I set a simpler goal: sign up for a handful of events and actually make it to the start (not finish!) line.

The year had other plans, at least at first. While I’m happy to share that I completed 6 of my cycling events this year, the road to get there was more challenging than I had expected due to a myriad of health issues.

A Rough Start

For those who haven’t followed some of my previous updates, nearly 15 years ago I was diagnosed with Crohn’s disease. Day to day it’s pretty well managed, but it comes with some side effects, and the biggest one for me has been managing my iron. Keeping my iron levels up has been an ongoing challenge, and when iron is low, everything on the bike just feels harder. I’m still working with my doctors on a long-term plan for it.

In late January I came down with an illness just as I was leaving from Scottsdale for work. It hung on through a second work trip to Las Vegas and developed into bronchitis, an ear infection and side pain that dragged into March. All in, that was about five weeks of being sick, including about ten days completely off the bike. I squeezed in two iron infusions somewhere in the middle of all that.

By late February my fitness in Intervals had hit its lowest point of the year. I wasn’t thinking about major events, I was thinking about breathing normally again and hoping to salvage some sort of cycling season for the year. March was the turnaround; I got back to riding consistently, had two more iron infusions in April, and worked through a shoulder injury that developed playing with my kids (of course!). I was grateful that I was able to overcome a rough patch and get back on a solid path.

The Numbers

  • Events: 6 (4 road, 2 gravel)

  • Total Distance: 708 km

  • Climbing: 9,261 meters

  • Moving time: About 28+ hours across all 6 events

  • Fitness: Up almost 80% from the February low to my September peak (see my activity page for more details!)

The Events

  • Goodride Gravel (May 9, Chilliwack, 110 km): The season opener, and one I’d done before. Of course, I came down with a flu and stomach bug in the two days leading into it, so I was feeling pretty crappy on the start line. I focused on pacing more evenly this time and got up every climb with no hike-a-bike. I didn’t beat last years time but felt stronger throughout the ride.

  • Fraser Valley Gran Fondo (June 7, Langley, 127 km): This ride started out in the pouring rain and was super slow, the kind of first hour where you question your life choices. The second half was a different story: I picked up the pace quite a bit, and it ended up being my fastest event of the year at just over 30 km/h average.

  • TCC Invitational (August 9, Port Moody, 105 km): A home-turf event with my club, the TriCity Cycling Club. Riding with people you know makes the kilometres go by a lot faster. It was also the hardest I pushed all year by normalized power, which made up for my extreme lack of attendance for group rides this year. Huge thanks to everyone at TCC for putting it on!

  • Tour de Victoria (August 15, Victoria, 156 km): Six days after TCC came the big one: my longest ride of my life, with 2,000 m of climbing and five and a half hours of moving time. This was my premiere event of the year, being able to cycle through the city where I spent a good chunk of my early adult life.

  • RBC GranFondo Whistler (September 12, Vancouver to Whistler, 123 km): My first time doing the Whistler Fondo! I was rolling to the start before 6 am. The headwinds caught me by surprise, but otherwise it was a really great day, and the scenery makes up for a lot. Had a great feeling finishing this one.

  • Sea2Sky Gravel Fondo (September 27, Squamish, 89 km): The final event and probably the toughest. It was the shortest on distance, but it packed in nearly 1,800 m of climbing. I punctured about 20 km in and honestly thought my day was done but I was able to cross the finish line. I was pretty cooked by the end of the year so this was honestly my least favourite event of the year.

A few other events were on the list. Ride for Water and the Bert Flinn Enduro lost out to the kids’ baseball and basketball schedules. The Whistler XFONDO was postponed by the organizers. I made a deliberate choice to spend more time with the family and the kids this year which meant I had to sacrifice a few events, and that’s OK!

Reflection

While I’m incredibly proud of each of the events that I completed, including the rides that I did for the second time - I’m just as proud that I was able to put together an entire cycling season. In February I didn’t think I’d be doing any of this. Getting from there to 6 events over five months, around work, family and everything else, is what I’m most proud of. Each event had a moment where it could have gone sideways: a stomach bug, a soaking start, a headwind, a flat tire. Each time it worked out.

If you’re riding with Crohn’s disease, IBD, or something similar, and wondering whether a big season is realistic: it can be. It just might not look the way you planned. Now it’s winter base miles, split between Zwift and dark gravel riding in a (hopefully) mild winter, and in January I’ll pick what’s next for 2027. My goal is to really focus on perhaps 3 of these rides and try to get a similar time or better. We’ll see!

Dylan Hansen
Cycling Data Pipeline

Cycling is my hobby, and a big part of why it works for me is that it gets me away from a computer screen. I spend my working life in technology industry, so getting outside on a bike for a few hours is the balance to that, and I'm protective of it. What makes these parts of my life interesting is that every ride produces a pile of data. Heart rate, power, cadence, elevation, GPS, plus everything around the ride like sleep and Heart Rate Variability (HRV) and how sore I felt when I woke up.

There's a thing I keep running into professionally, which is that data is the whole game now. Everyone wants to talk about AI models and agents, but the difference between an AI experience that's genuinely useful and one that's a party trick is almost always the data underneath it. Clean, structured, accessible. That's the unglamorous part nobody puts in the demo. So there's a certain irony in the fact that I ended up proving it to myself on my hobby. I have built a data pipeline for my cycling data that captures it using my phone, processes it using two key cycling applications and then allows me to use AI to analyze, query and act on my data.

And all of this data powers my activity.dylanhansen.ca site that I blogged about not too long ago!

One Device on the Bars

Everything starts with Cadence.app, which is what I use to record rides. It runs on my iPhone, and that's the entire point. I don't want another device to charge, update and sync while my phone sits in my pocket doing nothing. My phone is already the most capable computer I own and it's already coming with me. Cadence just lets me use it as the bike computer too. A few things make that actually work rather than just being a nice idea:

  • It integrates directly with Apple Health. Every ride lands with the rest of my health data instead of in a walled garden I have to export from.

  • The Apple Watch works as a heart rate monitor. No chest strap. I already wear the watch, so that's one less thing to remember, charge and wash.

  • The screens are endlessly configurable, on the fly. I can rearrange what I'm looking at mid-ride depending on whether I'm doing intervals or just spinning. Most head units make you sit down at a computer for that.

For mounting I use a Quad Lock and it's been great. I was skeptical about putting a phone on the bars and I've now done it over some genuinely rough pavement with zero issues. Case on the phone, mount on the stem, quarter turn to connect.

I will note that for MTB I skip the phone and just track with the Apple Watch. It still connects to sensors, so I'm not losing data quality. I just don't get a display or a HUD while I'm riding. Which turns out to be fine. On the road I want the numbers in front of me. On the trail I want to ride the trail and look at the data afterward.

Two Data Destinations In Parallel

From Cadence or Apple Watch, ride data gets pushed to two places at once: Intervals.icu and Strava. People ask why both, and the answer is that they do genuinely different jobs.

  • Intervals.icu is where I plan and analyze. Structured workouts, the fitness model (CTL, ATL, TSB), HRV, resting HR, sleep, mood, fatigue, soreness. It's where I decide what to do tomorrow and whether yesterday cost me more than I thought. A basic account is free (although it’s worth the $50 CAD / year to upgrade), the developer is remarkably responsive, and the API is wide open.

  • Strava is where I network and where the ecosystem lives. It's where I see what everyone else is riding, track my PRs, and keep a history going back years. It's also the data set that feeds other Strava-specific tools. I use ProBikeGarage to track component wear, which only works because Strava is sitting there as the source of truth for how many hours are on a chain.

Strava tells me what I did and who else was doing it. Intervals tells me what it cost me and what I should do next.

Asking Questions Instead of Reading Charts

Both platforms are now queryable with Claude. For Intervals.icu I built a Skill, essentially a reusable set of instructions that teaches Claude how my data is structured, what my zones and thresholds are, and which endpoints to pull. For Strava I use their MCP connector, which does the same job without me building anything. It’s been great to see Strava launch this MCP connector in the wake of blowback on API changes in the past few years. The result is that I stopped reading dashboards and started asking questions:

  • What's my HRV done since that last big week, and should I be doing intervals tomorrow?

  • Which routes haven't I ridden in six months?

  • Build me a plan for next week that respects a group ride Sunday and legs that are cooked.

Two things came out of that which I didn't expect.

  • The first is honesty about effort and recovery. I used to train on feel, which in practice meant training hard when I felt good and training hard when I felt bad because I felt guilty. Now when my HRV is well below baseline there's a number telling me to back off, and a number is much easier to accept than a vague sense that maybe I'm tired.

  • The second is route variety. I had years of rides sitting in Strava and was cycling through the same handful of routes out of habit. Being able to ask what I haven't ridden lately, and build something new against the terrain and distance I actually want, has made the riding itself more interesting.

A Saturday in May is the one I point to. I'd had a normal week, my form numbers said I was fresh, and the plan called for a couple of hours on the road on a weekend. My HRV that morning came in at 21, against 48, 54 and 56 the three days before. Resting heart rate was rising. Nothing obviously wrong, I just felt a bit flat, and in any other year I'd have ridden anyway and called it a bad day in the saddle. Instead I did an hour of yoga and nothing else. The next morning HRV was back to 42 and I rode out to Horseshoe Bay (a beautiful ride!), three and a half hours, one of the best rides I've had this year. That ride does not happen if I ride through the Saturday.

What makes that day stick with me is that the two data sources disagreed. My form numbers said go. My recovery numbers said don't. Knowing which one to listen to is the entire value of having both.

What It Adds Up To

None of this made me faster, riding does that. But it changed how I make decisions, and at 42 with a demanding job and two kids, decisions are most of the game. The hard part of training isn't the hard days. It's knowing which days are supposed to be hard.

And none of it works because the AI is clever. It works because the data underneath is clean and the platforms let me at it. Swap any piece for something closed or messy and the whole thing falls over, no matter what model you point at it. Same lesson I run into at work every week, just with better scenery.

I'm sure I'll keep tinkering with it. That does seem to be how all of these go!

Dylan Hansen
Claude Code - Dinner Helper

One of those small annoyances in our house is figuring out where to order from on a Saturday night. We end up rotating through the same few spots by default and half the time we're ordering from somewhere we just went to two weeks ago. I kept thinking there had to be a better way to solve this and it turns out the data I needed was already sitting in a Google Sheet the whole time.

So I built something to solve this! This is my second project using Claude Code as an AI coding partner (the first was my activity dashboard) and I'm really excited to share how it went.

The Idea

We use Tiller Money to track our finances in a Google Sheet. Every restaurant transaction is already categorized with a date. I wanted to build a simple mobile app that the whole family could use to get a suggestion for where to eat based on how recently and how often we've been to a given place. Places we haven't visited in a while should bubble up, places we just went to should get pushed down.

The result is a private, mobile-first web app. It's shared only with the family and it's been a fun little side project to tinker with.

How Claude Code Fits In

I’m an ex-developer turned AI-curious engineer. I can read code and I understand how things fit together at a high level, but building something end-to-end on my own would have taken me weeks of frustration and half-finished Stack Overflow rabbit holes. Claude Code has genuinely changed that for me.

What I've found is that it's not just about the speed (though that's real). It's about the quality of the learning. When I didn't understand why something was built a certain way, I could just ask and get a real explanation in context. When I pushed back on something feeling overcomplicated, Claude would explain the tradeoffs and we'd find a simpler path. I probably learned more about how Next.js App Router actually works this weekend than I had from months of casual reading.

The whole thing took about 6-7 hours spread across a couple of evenings.

Stack

  • Next.js 15 (App Router) with React 19 and TypeScript

  • Tailwind CSS 4 for styling

  • Upstash Redis for storing restaurant data

  • Claude Haiku for cleaning up merchant names

  • Google Apps Script for syncing the data from Tiller

  • Hosted on Vercel

How It Works

A Google Apps Script runs inside the Tiller Sheet every Saturday. It reads only the merchant name and date from restaurant-categorized rows (no dollar amounts, nothing sensitive) and sends that payload to the app. The app never holds any Google credentials which was an intentional decision Claude helped me think through. Basically if anything ever went wrong on the app side, the worst case is someone sees a list of restaurant names.

When new merchant strings come in that the app hasn't seen before, they get sent to Claude Haiku for cleanup. Tiller merchant names are pretty messy in practice. Things like Ls Woking Dragon, Coquitlam or White Spot #141. Claude strips the city suffix, removes branch numbers, flags venue concession vendors (Rogers Arena food stalls kept showing up under "Restaurants"!), and infers the cuisine type. It also picks an emoji and a color theme for each restaurant card in the UI which was a fun bonus. Results get cached permanently so the same string never needs to be parsed twice.

The Suggestion Logic

The scoring is pretty straightforward: score = 50 - recency_penalty + frequency_bonus

Heavy penalty if you were there in the last two weeks, lighter penalty within a month, and a small bonus for places you visit often because you like them for a reason! Anything you haven't been to in over a year drops off the list entirely. From the scored list the app does a weighted random pick so it doesn't just mechanically serve up the top result every time. Hit "Reshuffle" and you get a fresh draw from the same pool.

What I Actually Got Out of It

Beyond just having a working app, I feel like I came out of this project with a much better understanding of how serverless apps actually fit together. The data pipeline, the Redis caching layer, the scoring logic, the mobile UI with per-cuisine color themes... all of it came together in a way that I can actually explain and reason about now. That's the part I'm most proud of.

I'm looking forward to continuing to tinker with this and keep learning through building real things with Claude Code!

Dylan Hansen