Run 629: Moving muggy

Run 629
Average pace: 5:30/km
Location: Brunette River trail
Start: 6:11 am
Distance: 5.02 km
Time: 27:38
Weather: Sunny, clear
Temp: 26ºC
Humidity: 44%
Wind: light
BPM: 153
Weight: 164.5 pounds
Total distance to date: 4725 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (80 km)

I was not expecting much more than a standard sort of run tonight, as it was quite a bit warmer than the last few runs, but lo and behold, despite the mugginess, I was somehow still moving along and finished with a pace of 5:30/km and a surprisingly low BPM of 153.

My left foot was a tiny bit sore at the start, but it smoothed out quickly, and a stitch in my gut threatened, but never materialized, so other than it feeling kind of sticky, the run was fine.

In fact, I can’t really think of anything to add. Thursday looks to be about the same weather-wise, so we’ll see if the run follows. My prediction is I will be slower as the week wears on, but maybe not.

Also, that raccoon was not at the river today, which makes me happy, both for myself and the raccoon, because raccoons kind of scare me, really.

Run 628: A frozen raccoon, a snake and more consistency

Run 628
Average pace: 5:42/km
Location: Burnaby Lake (CW)
Start: 10:43 am
Distance: 5.03 km
Time: 28:39
Weather: Cloudy, some sun
Temp: 18-20ºC
Humidity: 70%
Wind: light to moderate
BPM: 161
Weight: 163.3 pounds
Total distance to date: 4720 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (75 km)

I was expecting to slow back down at the lake and I did, but I am still weirdly consistent, as my pace was 5:42/km, and the majority of runs at the lake (and some at the river) have been hovering right around this pace for some weeks now. I’ve peaked before but never so…precisely.

My tentative plan is to run counter-clockwise next time, even though it appears the side trail resurfacing still won’t be done (it is taking them a curiously long time). Speaking of, yesterday I scouted out the progress and took this photo where the Conifer and Spruce Loops intersect:

Spruce Loop looking a little footprint-y.

You may be thinking, “Why does a closed trail have so many footprints on it?” Given the erratic pattern, I’m assuming they’re from the workers actually spreading the gravel and not from trail rebels not letting little signs tell them where they can and can’t go.

Technically, one of the footprints is mine, as I tested to see how soft the surface is. It is very soft. I would not want to run on it.

But it looks like a lot of the Conifer Loop is done, with just some rolling remaining, while the Spruce Loop still needs some more top gravel placed and then rolled. Given the current pace of the work, I expect the side trails to re-open sometime next year. :P

Okay, maybe next month.

And speaking of pace, back to today’s run, in which I nearly stepped on a snake (good thing they move so fast without having legs). I felt perfectly fine, though I did notice the knees a bit early on. They weren’t hurting, I just noticed them, but my mind wandered off soon enough. Unlike the river, I did not have a fourth km blitz today–my fastest km was the first, as is traditional (next was the final km. I want to say I pushed a little, but I’m not sure I did). I treated the whole run fairly casually, not looking for a great pace, just a steady one.

After the run, I walked/jogged a recovery km, then ran the next with a pace of 5:30, which was actually faster than all but the first km of the actual 5K, so I was clearly keeping things bottled up.

It was humid, so I sweated a bit, but clouds moved in mostly just for the run itself, then parted on the walk back, which suited me fine.

Overall, this run was more of the same. I’m curious to see if my times actually start shifting more in one direction or the other soon.

Oh, and the raccoon. I was walking along the river trail toward the lake, about halfway there, when a raccoon came out of the brush on the left, which is the river side. It saw me and froze. I mean, it did not move at all. It became a raccoon statue. I also chose to stop, though with a less statue-like aspect. I paused my run, as I was not sure how long it would take the raccoon to come out of its trance-like state. Finally I got tired of waiting and made a grand sweeping gesture to the right, telling the raccoon it was free to go.

And then it did, hurrying off into the brush on the other side of the trail. It was a little weird. Also, I accidentally ended my run instead of pausing it, so I had to start a new one. This made me think the Done button at the end of the stats of the workout should have another button that says something like Continue Workout, because the End and Pause buttons are next to each other and hitting End doesn’t offer any confirmation, the workout just stops. This would let people have an Oops button and keep the workout going. (The current UI is actually better than it used to be. Originally there were two buttons, Save and Cancel. Yes, you could finish a workout, then accidentally tap the Cancel button and nuke everything you had just done. Brilliant! You now have to go into the Activity app on the phone to delete specific workouts.)

Run 627: The fourth km blitz

Run 627
Average pace: 5:26/km
Location: Brunette River
Start: 6:07 pm
Distance: 5.03 km
Time: 27:22
Weather: Sunny
Temp: 22ºC
Humidity: 47%
Wind: light
BPM: 155
Weight: 164.5 pounds
Total distance to date: 4715 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (70 km)

On the way to the start of tonight’s run I was thinking about how sometimes I’ll feel tired before a run and then go on to turn in a good performance, and other times the run will reflect that same sluggish level of energy. The latter actually doesn’t happen that often and I kept that in mind as I got ready, as I was not feeling super-invigorated.

It turned out I was secretly super-invigorated because I ended up turning out my fastest run of the year, finishing with a pace of 5:26/km. A large part of this came about due to a burst of speed in the fourth km, something I’ve noticed happening in several other runs recently, as if I’m catching my second wind or finding the perfect stride right around that 20 minute mark. In this case my fourth km was a blazing 5:04/km, the closest I’ve come to breaking the five-minute mark this year. And I emphasize that I was not trying to do this, I just felt good and kept the pace up (or increasing it, as it turned out).

I didn’t really push at all until the last stretch and by then I was slowing, with my pace dropping to 5:22/km. But it was the only time I felt even a little burn–and it was little. The rest of the run there were times where I felt genuinely light on my feet, as if I’d found that perfect rhythm or zone. My mind bounced over a succession of topics and in this case, a wandering mind is a sign of a good run.

My BPM was also low at 155. The conditions helped, too, as it was warm but far from hot after yesterday’s rain, and the sun was low, so I only got a few minutes of it. Humidity was reasonable, so sweating wasn’t excessive and I never felt dehydrated.

I’m surprised and kind of delighted by how well the run felt. The next one will be at the lake and I suspect it will not feel as effortless as this one, but I’ll bask in the glow for a few more days, at least.

Run 626: A cool effort

Run 626
Average pace: 5:41/km
Location: Burnaby Lake (CW)
Start: 12:16 pm
Distance: 5.02 km
Time: 28:33
Weather: Cloudy
Temp: 19ºC
Humidity: 67%
Wind: light
BPM: 160
Weight: 163.4 pounds
Total distance to date: 4710 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (65 km)

First, the strange news: Today’s run took me 28:33 minutes. The previous 5K run, which I did on the river trail, took me 28:34 minutes, a difference of one second. How I can manage such precision while running in two different locations is baffling and a bit unnerving. But yay for consistency when the result is good!

Now, the good news: It was much cooler and cloudy for today’s run, which made for a refreshing change of pace. Sweating was minimal and my energy felt strong throughout. I was actually a tad disappointed that I came in at the same overall pace as the previous run at 5:41/km. I was hoping I’d be faster–though the lake is a more technical run than the river, so there’s that.

After some contemplation, I chose to go clockwise yet again, as work continues on the side trails. There is more progress, though, as I could see the Conifer Loop has been resurfaced, complete with the top layer being smoothed into place. Hopefully they’ll wrap it up by next weekend.

I did not get off to a zany fast start this time, and the pace from one km to the next was a little more consistent–in line with how I felt. I thought of running more than 5K, but in the end wanted one more direct comparison, especially after missing a run. Post-run, I walked the first km, then ran the entire second km, with a pace of 5:41/km, matching my overall pace for the run. This is encouraging. I actually ran a lot on the way out, with no issues at all.

Overall, this was a nice effort. I felt good, had lots of energy, had no issues and it was not busy on the trail, likely thanks to the cloud cover.

Run 625: Made in the shade

Run 625
Average pace: 5:41/km
Location: Brunette River trail
Start: 6:16 pm
Distance: 5.02 km
Time: 28:34
Weather: Sunny
Temp: 26ºC
Humidity: 45%
Wind: moderate
BPM: 156
Weight: 165 pounds
Total distance to date: 4705 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (60 km)

I was going to run on Saturday but did some errands and then had a kind of lazy day after that (I did go for an hour-long walk, so not totally lazy). Sunday the weather was showery, so I waited for a break, but the weather never really changed, so I ended up having two lazy days.

Monday was Monday. I only run on Mondays when it’s a holiday.

Which meant I ran today, Tuesday, with a four day break in-between runs. Longer than I’d like, but on the edge of being acceptable. This was a post-work run, so I set off to the river trail.

It was not four degrees warmer than Thursday’s run, and humidity was lower, but the balance was pretty close, which meant I sweated, but not a lot, and my mouth did not turn into a mini-Sahara. It also helped that the sun was lower, so most of the run was in the shade. Yay shade.

My left foot was a bit sore to start (probably a posture thing–as I sit here typing this, I have my feet on a foot rest, but had my right foot resting on top of the left one, smooshing it in a way that’s probably not great), but it settled down quickly, and there were no issues after that.

BPM was similar to Thursday, but my overall pace was faster at 5:41/km. Curiously, the fourth km was by far the fastest, a zippy 5:08/km. I’m not sure why I was moving so swiftly at that point. Maybe I slipped into “must finish quickly so I can eat dinner” mode. By comparison, the previous km was 6:06/km. That difference is kind of crazy. Maybe I was so slow in the third km that I ended up being well-rested for the next one.

Overall, a fine run, with no apparent side effects from the four days off.

Run 624: Cooler and faster

Run 624
Average pace: 5:48/km
Location: Burnaby Lake (CW)
Start: 2:49 pm
Distance: 5.02 km
Time: 29:08
Weather: Sunny
Temp: 22ºC
Humidity: 57%
Wind: light to moderate
BPM: 157
Weight: 166 pounds
Total distance to date: 4700 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (55 km)

Today started out cloudy, which would make for a nice run. By the time I headed out it cleared up, but it was okay, because the temperature stayed around 22ºC, which is well below the threshold of “Why am I running in this crazy heat?” Humidity was higher, too, so unlike the previous run, I was not plagued by dry mouth. It was nice.

After the last run I had some soreness in my left knee, extending down into the shin, so I was concerned how this would impact the run. Surprisingly, it didn’t seem to have any effect, perhaps because the three days off gave it enough time to sort of recover. I didn’t experience any other issues during the run and at times I felt pretty good, even distracted enough to think about other things, as I do when I get in the proverbial zone.

My BPM was right around average for the runs of late and my pace was only a tick or two higher at 5:48/km, but also within range, showing that I was able to come back from the Xtreme Heat run without complication.

Officially I hit 4,700 km total today, though it’s higher, since I didn’t track runs from the start, but 4,700 is a pretty good number. It’s enough to get me to Honolulu with almost 300 km to spare, though my shoes might get a little wet.

The Sauconys have not been scooping up gravel the last few runs, leading me to believe this is more a me problem than a shoe problem. I’m not sure what has changed, but I’d like to continue not scooping rocks and debris into my shoes.

In all, a decent run. My next will be on Saturday and I may go clockwise yet again, as progress on the resurfacing of the side trails is moving strangely slowly, so they remain closed (this is doubly odd, because they never actually closed the main trails while resurfacing them, so I’m not sure what exactly they’re doing on the side trails. Maybe they’re adding more trees or something).

Run 623: The “Why did I run?” run

Run 623
Average pace: 6:08/km
Location: Burnaby Lake (CCW)
Start: 3:55 pm
Distance: 5.04 km
Time: 30:57
Weather: Sunny, hot
Temp: 30ºC
Humidity: 36%
Wind: light to moderate
BPM: 155
Weight: 164.8 pounds
Total distance to date: 4695 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (50 km)

I did not plan to run today, but I ended up running, even though it was kind of nutty to do so. Let me explain.

On Friday I planned to run, but slept in and then deferred to Saturday, as I did not want to run later Friday when it would be too hot. Remember the “too hot” part.

Later Friday I developed a pain in my abdomen reminiscent of “men of your age” infections of yore. Saturday morning, instead of running, I went to my favorite nearby walk-in clinic. Except they wouldn’t see me until noon, so I went back at noon. The diagnosis was vague and uncertain, though I had sugar in my urine, so the diabetes alarm was raised once again (this has happened throughout my entire life–so far each actual test has come back negative). The doctor gave me a bunch of other tests to take, similar to the ones my own doctor wanted me to take, but which I had been putting off, because I’ve been kind of lazy during vacation. She also suggested I drink lots of water and drink Metamucil, to prevent blockage/infection, though I assured her I was pretty regular already.

Sunday morning (today) Jeff drove me to a LifeLabs that was open on the weekend and they took more pee and also blood. The blood removal was the most efficient I’ve ever seen. It was kind of eerie.

After this, we went out for breakfast at IHOP (mmm, blueberry pancakes), then came home. I opted out of going to the Pride parade because the thought of sitting/standing ion place for hours on end did not seem enticing. Jeff ended up going off (unplanned) to watch it on his own.

It was very hot today. By mid-afternoon it was up to 30ºC. I decided if I couldn’t run, I’d at least walk, so I put on my running clothes (they are much more comfortable for warm weather) and set off to walk to the lake and back (around 8 km total). When I got to the lake, I decided to keep going, so I did that. When I got to Still Creek, I contemplated doing a run to finish off the loop around the lake. Remember, now:

  • it’s 30ºC
  • I had blood taken just hours earlier
  • I have abdominal pain

There was no good reason to run. None. But I had already missed two potential run days and didn’t want to miss another, so I made an agreement with myself to only run for as long as it was comfortable. If there was any pain/aches/fainting, etc. I would stop. And so I sent off doing what was essentially the reverse of my usual 5K clockwise circuit.

The first km was relatively zippy, considering the heat, coming in at 5:28/km. This changed and by the third km I was firmly in “Why am I doing this?” territory, with my pace way down to 6:39. I rallied and came back to 6:12 before wrapping up with 6:23 for the final stretch. This was one of those runs where I really wanted it to end.

Despite how I felt, I was fairly confident once I made it past the halfway mark that I would be able to finish. Fortunately, the Avalon trail was in shade at this time of day, probably the only thing that kept me going to the finish.

My mouth was very dry. Like, it was the Sahara in my mouth. To paraphrase America, the heat was hot. The humidity was high enough to make the air feel like a furnace, but not high enough to keep my mouth moist.

And yet the most interesting stat from the run was my BPM–a mere 155. This means that both my mind and body were being sensible. As I slowed, I did not push to maintain an unsustainable pace. I fell back into a slower, but steady pace and kept to that. I didn’t over-exert. I was smart! This is one of the few times I checked my BPM mid-run, too. If it had been crazy-high, I would have stopped, but it was pretty steady in the 150s throughout.

And the abdominal pain, though still there, is now a much more muted kind of ache, so it didn’t present an issue. Really, the only issue was the weather itself. And my decision to run in it. :P

That stitch in my side when running…

I’ve always assumed that when I get a stitch in my side while running it’s because I’m going too fast–basically pushing my body too hard and the stitch is my body’s way of saying, “Whoa, slow down there, partner!” Because slowing down would always seem to make the stitch go away.

It turns out that apparently no one really knows what causes these stitches because they haven’t been studied much. The consensus seems to be they’re relatively innocuous, not a sign of impending doom, and that even pro athletes get them. I have to admit, on one of my last runs I got a stitch and didn’t feel like I was pushing hard at the time, so my own theory may be so much hooey.

I’ll probably still slow down when I get them, though, partly because it still feels logical (to my mind) and also because running hard with a stitch is, in fact, hard.

Run 622: Like a speeding bullet, then like a regular bullet

Run 622
Average pace: 5:42/km
Location: Burnaby Lake (CW)
Start: 11:02 am
Distance: 5.03 km
Time: 28:39
Weather: Sunny, veiled cloud
Temp: 23ºC
Humidity: 57%
Wind: light to moderate
BPM: 159
Weight: 166.3 pounds
Total distance to date: 4690 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (45 km)

When I got to the lake this morning, I was planning another counter-clockwise run, but knowing I’d have to skip the first two side trails, I planned to start on the other side of the dam, near the 0K marker, for that all-important psychological boost of finishing the 5K at or before the 5K marker. Then I thought, “Why stop there?” and opted to start at the 10K marker, giving myself an extra 300 meters to play with.

But as I walked to my start point, I thought about the noise and stink of the work around the dam, and the torn-up main trail that I would have to navigate right at the start, then decided to run clockwise, so I made my way back to the fountain near the dam (still ahead of the 5K marker, but not by as much) and set off.

Conditions were nearly as humid as Monday and it was a little warmer, so I was sweating even before the run started. Then I sweated a whole lot more. I didn’t push hard at the start, but I also didn’t hold back or try to set a steady pace, I just ran at whatever speed I felt comfortable with, then slowed down after.

As it turned out, my first km was a relatively blazing 5:14/km–this is the closest I’ve come to breaking the 5:00/km mark in a long time (and is something I doubt I will break, unless I specifically set out to do so). I’m not sure why I was so zippy, but that first km is why I ended up with an overall improvement of five seconds on my average pace, because every other km ranged between 5:41 and up to 5:58. My slowest km was the third and to be fair, I did improve in the following two km, so after burning hard and fast to start, I found some reserves to pick the pace up a bit for the back half of the run.

There were no issues otherwise, and the trail was relatively quiet, just a few other joggers and walkers, not even many people out walking their dogs. I managed to run a good bit after, even beating my average walk pace (8:02 vs. 8:28) vs. Monday.

I did actually rest after the run on the bed for about 20 minutes or so, because did I mention it was humid? I felt a little more tuckered, as a result, though I am up and aboot now.

I’ll probably run clockwise again on Friday, but we’ll see. They are predicting light rain, so that would be a relative novelty for a summer run. It might be refreshing, or horrible. Hard to say.

Run 621: Sweaty, tricky feet, snakes, gravel in shoes

Run 621
Average pace: 5:47/km
Location: Burnaby Lake (CCW)
Start: 11:30 am
Distance: 5.02 km
Time: 29:07
Weather: Sunny
Temp: 21ºC
Humidity: 61%
Wind: light to moderate
BPM: 159
Weight: 165.6 pounds
Total distance to date: 4685 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (40 km)

It turned out that since smoothing down the damaged part of the main trail leading to the Spruce Loop, still being resurfaced, the park workers have since resumed work and have re-damaged the main trail again, which made the first minute or so of today’s run a bit tricky, given that the trail was filled with unexpected ruts, piles of dirt and was also in one of those sun/shade areas where your eyes don’t have time to adjust to the ever-changing lighting.

But my tricky feet somehow got me through and I completed a counter-clockwise 5K today, surprising myself by coming in six seconds faster than Saturday’s run and proving that I am not as freakishly consistent as I could be. My pace was 5:47/km and this time the only issue I had was sweat and plenty of it. It was 21ºC, so actually a bit cooler than the last few runs, but humidity was way up, so I sweated early and often. No real dry mouth, the one benefit to a sticky, humid run.

My BPM was up, but only slightly, and I had a very steady pace, save for the second km, where I dipped a little before resuming my previous pace. Overall, I felt good, and managed to do a fair bit of running post-run as well.

I saw a snake ahead of me on the second boardwalk and as I approached, the snake slithered between the boards and out of sight. I wonder if the snake had any idea where it was going or was just confident that anywhere but under my approaching foot would be a better place to be. I saw another snake on the previous run, doing that “slither across the path in a panic as a human approaches” thing. I have not seen any pythons so far this year.

As for the gravel in shoes, it appears the new Sauconys share the same property the Brooks Cascadia 12s have in how they can effortlessly scoop gravel up and deposit it into the shoes. Like the Brooks, it happens almost exclusively while walking, so clearly there is something about my exercise walking gait that makes this a lot more likely to happen than when I run, which is preferable if it has to happen at all.

But today I stopped and emptied gravel and grit out of my right shoe three times post-run. It’s getting a bit silly. I still like the shoes, though.

I’m starting to think about trying a 10K soon, maybe before my vacation ends. I’ll see how the next few runs go before committing, as any 10K will have a horrible long time and will leave me a little depressed, even if it goes as well as can be expected. Basically, my body is probably ready now, I’m just not sure if my mind is.

Run 620: The consistency is getting strange

Run 620
Average pace: 5:53/km
Location: Burnaby Lake (CW)
Start: 2:20 pm
Distance: 5.03 km
Time: 29:35
Weather: Sunny with some cloud, windy
Temp: 24ºC
Humidity: 45%
Wind: light to high
BPM: 157
Weight: 165.4 pounds
Total distance to date: 4680 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (35 km)

Thanks to running on Thursday instead of the planned Wednesday, I ended up running today–a Saturday–when I didn’t want to. I prefer weekday runs because of the smaller crowds on the trail. Weirdly, crowds were not an issue on the trail today, as it was not that busy, despite quite nice weather.

Although temperature was similar to Thursday, it was quite windy at times, but generally in a good way, with the breeze feeling cool and pleasant, not something I was fighting against. My mouth didn’t even feel particularly dry, something that’s generally been the case so far this summer.

I felt a bit of a stitch in my lower left abdomen early on, but kept steady and it went away. No other issues during the run, with the knees again fine and the sore left foot feeling better.

My energy level was also the best of the last three runs, and I did not feel tired even during the final km. This was reflected in my BPM, which dropped from 161 to 157, a nice improvement and a sign that my stamina is improving at last.

What was weird was my pace–5:53/km. This is identical to my previous run and only one second off the run before that. I don’t think I’ve ever had such a set of eerily consistent runs. The total time of today’s run and the previous is separated by three seconds. I could never be this precise on purpose. Think about it. If you break the run down to seconds, this is how they compare:

Run 1: 1772
Run 2: 1775

That is a 0.17% difference, which is ridiculous.

Although I am tempted to do a fourth clockwise run around the lake just to see if this would freakily happen again, I am leaning toward counter-clockwise, as they have done a bit of remedial work on the section of the main trail that got trashed as they resurfaced the side trails (which is still ongoing). It’s been quite awhile since I’ve run counter-clockwise and bypassed the side trails, so it will feel a bit different and I’m all over the novelty factor.

Overall, today’s run was solid. The pace was unchanged, but I felt better, my BPM was lower and I had enough energy to run multiple km afterward, even coming close to matching my 5K pace.

Run 619: The same but different

Run 619
Average pace: 5:53/km
Location: Burnaby Lake (CW)
Start: 11:25 pm
Distance: 5.02 km
Time: 29:32
Weather: Sunny
Temp: 23ºC
Humidity: 51%
Wind: light
BPM: 161
Weight: 166.2 pounds
Total distance to date: 4675 km
Devices: Apple Watch Series 2, iPhone 8
Shoes: Saucony Switchback ISO (30 km)

It was not quite as warm today as Monday, but I ended up sweating more because the heat/humidity mix was leaning a little more to the “you’re going to sweat” side of things.

Today’s run was interesting in how much it was the same, yet different, than the previous one.

BPM was identical at 161. Average pace differed by a mere second, and total time by only 10 seconds. Spread over 5 km, that’s pretty tiny.

The difference today was in how the overall run played out. I started faster and ended faster, but found a steadier, but slower pace in-between the two. This made for a run that felt a lot more comfortable. I felt perfectly fine until heading into the final km. At this point when running clockwise at the lake, the trail is pretty open, meaning the sun is beating down on you most of the time. I was also starting to get a wee bit tired, and the extra exertion to maintain pace was being felt. It still wasn’t bad, though, and certainly not like Monday’s run.

And yes, I meant to run yesterday, but I had an intense bout of vacation laziness I could not overcome.

The left foot was again a bit sore starting out, but not too bad after. I wonder if the orthotic is starting to just get old and I’m feeling the True Foot Experience more now. Maybe I’ll follow up on that next week.

Conditions were otherwise good. A few runners, some walkers, one over-exuberant and unleashed lab (I called out to the owner my favorite three words for dog owners: Leash your dog. I did this twice, to make sure she heard. I don’t think she did, if you know what I mean.)

Another difference with today’s run vs. Monday’s is how I felt after. Monday I was pooped and made a few token efforts to run after finishing the 5K. Today I walked the first post-run km, then ran almost the entire length of what would have been the 7th km of the run. I repeated this a few times, running for longer stretches than normal. I felt positively zippy, which bodes well for the eventual tackling of a full 10K (possibly soon™).

Overall, a good run, despite the deceptively minimal change in performance.