A surprisingly strong flat run with Paula and Laura on bikes, built on the heavy combo of run #32 plus a big Portola Valley–Borel Hill ride one week earlier and boosted by a lot of proud‑dad energy.

Run #33 was special even before I started my watch. I had both Paula and Laura on bikes with me, a rare alignment now that Laura had just graduated in Electrical and Computer Engineering and was about to head off on her post‑graduation vacation. Having them both in town and willing to ride along turned this outing into more than just another entry in the 52@52 challenge; it felt like a small family celebration on wheels and legs. The route followed flat paths near the water in the South Bay, similar to other Bay Trail segments that welcome runners and cyclists along the shoreline.

What made this run memorable was how light everything felt, despite the heavy week that preceded it. In the previous weekend’s run #32, I had pushed hard to stay close to Bebeto’s marathon‑level pace and ended up going beyond the half‑marathon distance, closing the day at 14.95 miles instead of 13.1. The very next day, we added a 23‑mile bike ride with about 1,363 meters of elevation gain, starting from the base of Portola Valley and climbing all the way up toward Borel Hill in the Santa Cruz Mountains. Borel Hill tops out around 2,572 feet (783 meters) and is known for its views over the South Bay, and reaching that height on the bike is a serious effort. That combo of long run plus long climb on the bike loaded the legs early in the week, but by the time run #33 arrived, the fatigue had transformed into strength.

There is good rationale behind using cycling this way as part of a running block. Coaches often point out that low‑impact endurance activities such as cycling can help build aerobic capacity and muscular resilience without the same pounding as additional hard runs, and that sprinkling one or two cross‑training days into the week can improve recovery between intense running sessions. The trick is to keep hard days hard and easy days easy, letting demanding efforts like a long climb be followed by adequate recovery so the adaptations can “sink in.” In my case, that sequence – a tough long run, a big bike climb the next day, and then a few days of normal life before run #33 – seems to have worked exactly in that way, leaving me ready to run fast and comfortably when the next challenge came.

Out on the flat South Bay route with Paula and Laura cruising beside me, the pace was fast for my standards but felt smooth rather than forced, with no aches and no sense of fighting the distance. Having my wife and my newly graduated engineer daughter riding as support crew added a strong emotional tailwind; every kilometer carried a mix of pride, gratitude, and the quiet joy of seeing family and personal goals meet on the same path. Unfortunately, my son did not join us this time, although I know this kind of outing is not really his thing at the moment — even if, when he was little, he did a few triathlons with a school team, which shows that the connection was there once. For the 52@52 challenge, run #33 will stay in my memory as the day when a heavy training week turned into a light, joyful run, and as a hopeful preview of a future outing with the whole family together — fingers crossed.