Seen this morning, after my side trek to the Brunette River. This is a very vibrant hydrant and I could not not take its picture.


Her name was Ms Anderson, and she was the first teacher I had who went by Ms. She was very modern. I took Foods and Nutrition (a fancy name for Cooking) with her for Grade 8. Back then–the late 1970s–cooking was still widely perceived as a “girl/woman” thing1I made history at my junior high by being the first male recipient of the year-end cooking award in the groovy year of 1978. This was reflected by my class only having four guys in it (I was one of the four).
Looking back, the three things I remember most were:
The other two were things Ms Anderson said:
So a thanks to Ms Anderson. She was young, so might only be in her 70s now, probably retired. I’d love to hear the kinds of stories she’d tell.

I’ve been using my Garmin Forerunner 255 watch for about a year now and mostly I quite like it for my runs. I get a nice array of stats, it presents lovingly in a web interface, as well as in the requisite app. It performs well and remains easy to use in all kinds of weather. It’s accurate.
Well, it was accurate until today.
As you can see by the chart below, my heart rate went up rather dramatically right near the beginning of the run, when my BPM is usually on the lower side (since I’m just starting my workout). It then stayed really high (pushing 190) for a little over the first km before abruptly dropping down and staying in a typical range for the rest of the run.


I first suspected something was up at the end of the first km, when I got my usual performance conditions alert. This puts together various stats to give me a rating of how the run is expected to go. I usually see it fall in a range of -1 to +2. Today it reported -9, which I think would normally mean it was making the assessment when I was still laying in bed at 6 a.m.
I did check my heart rate later in the run several times, when it reported 151 and 155. I think 155 is probably close to the actual overall average.
At the end of the run I got a message about how it had “adjusted” my heart rate somehow, along with a context-free “+180” and I still have no idea what the +180 was referring to. I can’t find the message now and wish I’d taken a photo of it with my phone, but alas. The best I can guess is it was adjusting the overall heart rate based on the spike, making it 160 overall.
But mainly I think the sensor wigged out for some reason. I’ll probably power-cycle the watch or check for updates before the next run, just to be thorough (though once it settled back down, it was fine, and reported normal activity for the 4 km walk home).
As for the actual run, I had four days off, so I was feeling a little rusty, but no issues to report otherwise. It was drizzly, and my glasses started getting coated, but at least it was much milder than Friday’s run. This was also the first run since the storm bearing an atmospheric river came through, and sections of the trail were either washed away or in otherwise rough shape. A quite large tree at the start of the Spruce loop did not survive:

The freaky heart rate kind of spooked me, even though it was almost certainly a sensor glitch (I checked as I was writing this and there is, in fact, an update for the watch due out today or shortly after), but the run itself was pretty normal for four days off.
Stats:
Run 835 Average pace: 5:47/km Training status: Maintaining Location: Burnaby Lake (CCW, short loop) Start: 9:42 a.m. Distance: 5:03 km Time: 29:04 Weather: Cloudy, drizzle Temp: 8-9ºC Humidity: 91% Wind: light BPM: 1601See the explanation below for this (probably more like 155) Weight: 169.8 Total distance to date: 6065 km Devices: Garmin Forerunner 255 Music, iPhone 12, AirPods (3rd generation) Shoes: HOKA Speedgoat 5 (200/368/568 km)

Tonight, I said to myself, “What should I do? I already had a shower, what else is there?” And then I noticed that Windows had an update available. It always does. I installed it and it needed to reboot. It always does.
I used the opportunity to jump back over to Linux Mint and girded myself for the billion updates I’d skipped last time. They completed, but it then required…a reboot. I guess Mint always does, too.
I rebooted.
I then spent time tweaking the whole system, installing extensions and applets, slapping on a new dynamic wallpaper so it doesn’t look like a clone of my Windows desktop. It looks fairly snazzy now. I get weirdly hung up on visuals, so this is important to me.
I copied over my music library to the dedicated SSD for Mint, so I could listen to (non-streaming) music. I am doing so as I type this.
The best part, though, is I don’t have any version of Bejewled available on Mint. This increases my productivity by about 1000%. I may have a bit of a Bejeweled problem.
Anyway, things are working, and the system feels a lot more solid now. Will I stick with it and use it more than my previous attempt? Maybe!
YAM = Yet Another Mint
We just had one of those fun atmospheric rivers come through the area, and they always live up to the name, dumping huge amounts of water before moving on.
This afternoon I made a trip with my camera to Lower Hume Park and found the field to be squishy, muddy, and very marsh-like. There were ducks.
And seagulls and crows. And up top, some golden-crowned sparrows and several elusive juncos. The light was not great, but I got a few decent shots (I’ll post more later). Here’s a crow I shot on the way back home:

And a shot of the still very high Brunette River:

Spotify has been in the news recently, and it has not been good news:
On the second item, I do wonder why they needed so many people. Like many tech companies, they got silly with hiring during the pandemic, so some cuts were inevitable.
But the layoffs, Uruguay demanding fair payment and Spotify essentially saying, “We can’t pay artists fairly and also survive” made me wonder if we’ll eventually reach a point where music streaming transforms from what it is now–a frankly shockingly inexpensive way to have what is essentially endless music–to something else. Some possibilities:
Of the above scenarios, I think the first–price increases–is the likeliest. And we’ve already had some recently. I’m sure more are on the way.
Yes, I finally put some photos together. Enjoy!
Where: Centennial Beach and Boundary Bay Dyke Trail (Tsawwassen) Weather: Sunny, 8-11°C
The Outing
The first birding of December was pleasantly sunny and mild, though we got a late start, due to me having an appointment to get stabbed multiple times in my left arm.
After the stabbings, we headed to Centennial Beach, and we saw an actual raptor in the vicinity of Raptor Trail. We also saw various bald eagles, some in trees, some flying too high to really get good shots of. I got probably my best eagle butt shots ever (it was sitting above us in a rather tall tree).
Sparrows proved to be surprisingly plentiful here, as well later along the Boundary Bay Dyke trail. The light was low and a bit golden even from the start, but we made due. We skipped the usual journey onto the mudflats, as the tide was in, but spied numerous shorebirds further out, including dunlins that kept flying about, dwarfed by the occasional seagull towering over them. There were even rarely-seen surf scoters, but they were far enough out that they just looked like duck-shaped blobs through my telephoto lens. Too bad, because they are seriously freaky looking.
By the time we arrived at the dyke trail, the sun was quite low, but we pressed on to The Big Pond™ near a private residence…that proved to be waterfowl-free. Bummer! The adjacent and smaller pond on the western side of the property was populated prodigiously with perpetually propelling and peeping wigeons, mallard and others, however. The wigeons, as in our previous outing, were constantly nipping at and chasing each other. Maybe they are going through the wigeon equivalent of Pon Farr.
By the time we reached the pond, the sun was already sinking over the distant trees, but it did mean we got our first set of sunset shots in a while. We got back to the car three minutes after sunset and returned for dinner in darkness…at 5 p.m.
The Shots
Soon™
The Birds (and other critters)
Sparrows and sparrow-adjacent:
Waterfowl:
Common:
Raptors:
Non-birds:
Click and behold.

Looking at the forecast, there was no way I was going to avoid the rain today unless I just didn’t run at all.
Which I gave some thought to.
But I did run, and it did rain steadily throughout–while only rising to a chilly 3C.
I wore shorts (which were fine–the walk to the river trail was a little chilly, but not too bad) and my long-sleeved shirt with my OR jacket. The OR jacket did a pretty good job of keeping me dry. When I got home, I found only a few light damp spots on my arms and chest, almost like a light (if very cold) sweat.
As for the run, it actually went better than expected. Despite the chilly conditions, my BPM was a nice 151, without any weird spikes, and my pace was 5:43/km, just edging my fogariffic Wednesday run. There was wind, so visibility was not too bad. There was a lot of puddle dodging and for the first 2 km, I kept the hood of the jacket up, which produced a strange, rhythmic sound as I ran. Eventually, my head bobbing was jostling it enough that I finally pulled it down. I actually preferred having it down instead of weirdly bobbling on top of my head.
There were a few others out getting soaked, including the guy I now call Green Shorts. He apparently starts his route somewhere in the Sapperton neighbourhood, as I passed him post-run in Lower Hume Park. He was not just wearing his green shorts again, he was entirely green, so maybe he is also a leprechaun or just prepping really early for St. Patrick’s Day.

Anyway, the run went better than expected, so I am pleased. I am also still frickin’ cold as I type this, so a nice shower is next.

Stats:
Run 834 Average pace: 5:44/km Training status: Productive Location: Brunette River Trail Start: 10:07 a.m. Distance: 5:03 km Time: 28:48 Weather: Rain Temp: 3ºC Humidity: 96% Wind: light BPM: 151 Weight: 169.5 Total distance to date: 6060 km Devices: Garmin Forerunner 255 Music, iPhone 12, AirPods (3rd generation) Shoes: HOKA Speedgoat 5 (195/360/555 km)