The no-miracles post-vacation run

Run 347
Average pace: 5:18/km
Location: Burnaby Lake (CCW)
Ran Spruce and Conifer Loops
Distance: 10.04 km
Weather: Cloudy with some sun, a few sprinkles; humid
Temp: 20ºC
Wind: light
Calories burned: 772
Total distance to date: 2917

My first week back to work meant I could only run after my shift was over and every day it was pretty much Africa hot except Friday and by then I decided to just run Saturday morning instead and get a full run in instead. With a week between runs, I expected to be soft, flabby and slow.

Instead my pace was nearly identical to my last run, only one second slower at 5:18/km. Conditions were fine, with the temperature staying a moderate 20ºC, a nice breeze blowing at times and a mix of cloud, sun and the occasional light sprinkle.

My left foot was feeling sore before the run–never a good sign–and it became a factor past the midway point. By the 7K mark it was starting to hurt and it probably affected my pace in the last few km. I did turn it up a little for the home stretch but fell a bit short of my opening pace.

By about the 6K mark I began feeling tired and my pace fell off. It never cratered but I clearly did not feel as zippy as I might have. This run also marked the first time my all-time average pace went up, from 5:12/km to 5:13/km. Ouch. My average for the month is 5:20/km and with only one more possible run to go it’s unlikely to change. Alas.

Still, considering a week is a long time in running, I can’t be too disappointed. And on a more positive note this is the first month in a long while where I ran more than 100 km. Woot.

Mysterious Adobe offering

After being prompted to update Adobe Flash Player (this is the patch that makes it fun slightly more secure), the Adobe website redirected me to this page:

Adobe mystery product
Like a polar bear in a snowstorm.

You know, I just can’t say if I am interested in this product. Seems a little spartan.

News stories that make you wonder if these will be known as the pre-plague days

This is the lead-in to a news story on Ebola from the CBC News website:

Liberian officials fear Ebola could soon spread through the capital’s largest slum after residents raided a quarantine centre for suspected patients and took items including blood-stained sheets and mattresses.

Living in a slum sucks. Living in a slum where your neighbor has lifted blood-stained sheets and mattresses from an Ebola quarantine center probably does not improve things.

It will be interesting/terrifying to see how far Ebola has spread through Africa (and the world?) a year from now. Currently there is no cure for it, which is why it’s the go-to virus for a plague movie. Which we may now be living in.

My hometown: Lost in the clouds

Apparently some pernicious low-lying clouds were passing over my hometown of Duncan, BC when the satellite photos used by Google maps were taken, because the whole town is covered in what looks like a white film, regardless of zoom level:

Cloudy Duncan

I discovered this when checking out a news story about a small plane crash on a golf course near the Cassidy airport south of Nanaimo. Whenever I check something on Google maps I always end up checking other places. I think Google wants this to happen because in some way they monetize this. Perhaps I should be booking a hotel on the island right now or something.

You vs. a black bear: the infographic

The CBC News website ran a story on how to survive a black bear encounter (not to be confused with an encounter with Bear) due to a number of unusual bear goings-on of late. They included an infographic that I find strangely adorable and am reproducing here:

Bear Survival Guide

I like the idea of singing, clapping and whistling while hiking, to both ward off bears and convince other hikers that you are a lunatic. Also, the last image suggests using karate on the bear, which would be pretty cool.

[spoiler title=”And now the absolute best cover of Bear: The Novel” icon=”plus-square-1″]Bear[/spoiler]

Various commutes delayed on account of SkyTrain

It’s Black Eye Week for SkyTrain!

On Wednesday there was a problem with a switch at Waterfront Station that forced them to use only one platform during the early morning rush hour. I ended up being twenty minutes late for work (only five in reality as I normally get in fifteen minutes early). The worst part about this was the constant announcements with Mr. Stammer from SkyTrain control. Tip: Write down what you want to say, then read it into the PA. Don’t think off the top of your head every fricking time you turn the PA on. As outages go, this was pretty minor compared to the previous two.

On Thursday the PA system hummed to life as soon as I sat down in a car on the Canada Line at Waterfront Station. Never a good sign. Mr. Stammer said there was a minor power issue in Richmond and delays would be minor, only a few minutes at most. My train, whose ultimate destination was YVR-Airport, headed off. A few minutes later, when the issue should theoretically be resolved, Mr. Stammer came back on and was all, “Hoo boy, nope, this is a major power problem. Richmond is hooped! We’re setting up a bus bridge between Marine Drive and the airport. Sorry. We’ll figure this system out one of these days, lol!” My train’s destination suddenly changed to Marine Drive. That’s the stop after mine so apart from delays amounting to a mere five minutes, I wasn’t particularly affected by this. The overall delay for those who were affected amounted to around thirty minutes. Again, relatively minor compared to the Mega-Outages but still, you start to wonder how much duct tape is involved in holding everything together here.

Commute cancelled on account of SkyTrain

Four days after I missed a run due to a massive breakdown in the SkyTrain system…there was another massive breakdown in the SkyTrain system. Fortunately Jeff was listening to the news on the radio (remember those?) and heard the whole thing had gone on the fritz yet again and he swung over from his work site to pick me up. As a result of getting a ride home in the truck I was actually 15 minutes earlier than usual instead of four hours later. Nice!

As to the issue, I quote from the Translink website (emphasis mine):

Human error led to yesterday’s Millennium and Expo Line disruptions.

An experienced electrician was installing a new circuit breaker for the Evergreen Line at a power distribution panel when he accidently tripped the main breaker feeding the critical systems at SkyTrain’s operations centre, causing a system-wide shut down of train controls.

One can only imagine what an inexperienced electrician might have done. Burned down the operations centre and taken the system offline for several years, perhaps. (Note: the worker has been suspended but union reps are saying the worker was following the orders of a supervisor and the panel shouldn’t have been worked on during SkyTrain operating hours.)

The Vancouver Sun offered this in one of their stories on the breakdown (emphasis again is mine):

TransLink spokeswoman Jiana Ling said passengers involved in last Thursday’s shutdown were trapped for an hour and a half, but it appears those involved in Monday’s incident were more impatient, with many forcing the doors open after just half an hour. One of the doors was pulled off with a crowbar, Kelsey said, which prolonged the delay by two hours because trains won’t operate if a door won’t close.

Tannis Steele, 18, who was stranded Monday on an air-conditioned train near Main Street-Science World Station, said her fellow passengers broke out after half an hour because they were bored.

I’m not sure what to make of passengers on the SkyTrain carrying crowbars with them. But I’m not the slightest bit surprised it only took half an hour for someone to pry the doors open and get out and the rest following, yes, like sheep. And delay the system starting up even longer. Good job, people. Good job, indeed.

And my favorite image. I call this one Mother of the Year:

SkyTrain mom
Mom and the kids out for a walk on the light rail line.

I’m curious why she thought it was better to carry the kid under her arm than put him/her in the stroller. And the mind positively boggles over what she would have done on the Millennium Line where there is a fence going down the middle of the guideway area, preventing things like strollers from even fitting.

All in all, another terrific day for public transit in the Lower Mainland.

Run cancelled on account of SkyTrain

On Thursday I began my commute home at 4 p.m. as usual with the plan to do my run before dinner, meaning I’d be heading out around 5:30 p.m. or so. I get home around 5:10 or so and need about twenty minutes to recover from the stupor that results from an hour of riding public transit.

Everything proceeded normally on the Canada Line, so-named because its route from downtown Vancouver to Richmond is just like crossing Canada if you turned the route east-west and added 4,000 km to it.

All proceeded normally on the Expo Line until my train began approaching the Royal Oak station. Sometimes during peak hours trains will stop outside stations because there are so many of them running and they need to give them a minimum safe distance between each other. This usually happens at the busier stop like Waterfront or Commercial-Broadway but it can theoretically happen anywhere so I didn’t take much notice of it.

Shortly after the train stopped the P.A. crackled to life. This immediately triggered my “Uh oh, what broke on the SkyTrain?” alarm.

As it turned out, it was a major computer failure affecting a great swath of the system: all of the Expo line east of Metrotown (Royal Oak being the first station east of Metrotown) right up to an including Braid station on the Millennium Line (Braid is one station past where I get off at Sapperton), as well as the Expo Line spur into Surrey. The fact that the first announcement used the word “major” was bad.

At this point I would normally be about 12 minutes from my final stop of Sapperton. It was a few minutes before 5 p.m.

SkyTrain no go
Like ships not passing in the night because ships need to be moving in order to pass.

Not too long after the initial announcement another came on advising people that this was a “long term” issue and to stay on the trains. Do people actually get out of the trains between stations when the system goes down? As it turns out, yes, they do. Because people are impatient and dumb.

More announcements followed, reiterating what had happened and emphasizing that we would be stuck for a long time and to not get out of the train because then they have to cut power to the whole system to avoid electrocuting idiots and that will only delay things further. No one left my car, fortunately, but some reacted less favorably to the delay than others, as you will see.

My inner English teacher was irritated by the repeated use of the phrase “long term” to describe the problem. Merriam-Webster defines long-term as “occurring over or involving a relatively long period of time“. An outage, even one lasting hours, doesn’t seem to qualify. I almost expected a follow-up announcement advising passengers that “Your train will be delayed for several days. We please ask that you do not leave your train or eat your fellow passengers. We are working to airdrop supplies including food and deodorant.”

About twenty minutes in we were told that workers would be manually bringing in trains to stations and it might take awhile, in case we hadn’t figured that out yet. Oh, and also please don’t leave the trains because we already told you and you’re not listening. It’s only been twenty minutes, people, it’s not quite time for The Lord of the Flies yet.”

Shortly after this announcement I noticed someone using the emergency phone at the other end of the car I was on. Most people on the train were quiet–possibly conserving energy to prepare for the upcoming battle over supplies–so I could hear what he was saying and what he was saying was that a woman was starting to hyperventilate. I looked but couldn’t tell who he was referring to and entertained the idea that he was fibbing to get our train bumped to the top of the “please get us to a station before Survivor starts at 8 o’ clock” list.

It worked! A minute or so later an announcement for our train only informed us that we would be taken back to Metrotown station where emergency services would be arriving. By this time I could see the woman in question and she did not look so good.

The train them hummed to life and rolled back into Metrotown station. Incredibly people tried to get on the train, even though it was going nowhere. This was half an hour into the shutdown and anyone still in a station knew what was happening. As I got off the car I saw the woman was now face-down on the floor. I hope she was okay. I think she was probably okay. She may be riding the bus for awhile after this.

Metrotown has one of the largest bus loops in the system and it was already a sea of people. I finally found the end of the line for the New Westminster bus, the closest that would get me sort of home. It took over 40 minutes for the line to move to where I was close enough to actually be guaranteed a spot on the next bus.

Some people apparently or conveniently could not find the end of the line and formed a blob of people beside the bus, effectively cutting in. This became apparent and after the bus pulled up it sat for minutes without letting anyone board. You could sense tension in the air, along with a lot of body odor. Some in line noted the others not in line and called out to them. One woman started calling out “Shame on you! Shame!” I felt like I was in a European film. A transit officer arrived and tried as diplomatically as possible to tell the blob of people that they were totally cheating and we’re onto you. Some moved back, some stood their ground.

A man in the blob called out, “You can’t even see where the line is! How are we supposed to find where it is?” Several others in the blob murmured agreement. I wondered how the hundreds of people already in the line managed what these people had not but chose not to express this thought out loud.

We were finally allowed to board. It was now 6:47 p.m. I managed to get a seat at the back. The bus driver noted construction on Kingsway (more delays? Sure, why not?) and asked people to be nice to each other and to the bus driver. He said someone pulled a knife on the previous trip. Because pulling a knife works wonders for reducing an already tense situation. The passengers on my bus were either knifeless or not inclined to flash their blades.

The worst thing I had to deal with was the sturdy man sitting next to me constantly falling asleep and slumping onto me. Did I mention he was sturdy? He was, especially when he slumped into me, which was often.

By the time the bus rolled into New Westminster station it was after 7:30 p.m. I would need to walk up the street to Columbia station and catch a bus there that would kind of sort of go through my neighborhood. I was tired and hungry and called my partner and made puppy dog eyes over the phone. I told him it would be way faster for him to pick me up than me taking another bus and we could eat sooner and aren’t you hungry? He agreed.

Shortly after leaving he called back to report an accident blocking the main route. I wouldn’t be surprised if the SkyTrain was somehow responsible. He took an alternate route, I walked a few blocks down and finally got in the door a few minutes past eight.

My commute took four hours, roughly four hours longer than normal. The CBC website has a brief, lazy write-up of the story here, the centerpiece of which is a bland complaint from Twitter. While the story is no great shakes, the comments are predictably even worse.

At least in this modern age we can all ignore the strangers we’re forced to hang out with thanks to technology. A massive failure of the transit system may be inconvenient but it’s no reason to stop checking Facebook on your smartphone instead of talking to the person squashed into the seat beside you on the bus. I confess, I played Threes on my iPhone for most of the bus ride. I’m part of the problem.

After finally having dinner it was, of course, far too late to do a run, the second time in less than a week that a highly unusual event has caused a run to be postponed. And hopefully the last for awhile.

Despite all this, the SkyTrain is still way nicer than riding the bus. When it actually works.

Run cancelled on account of sun

Yesterday I bought a pair of fancy new Nike shorts for running because my current pair are starting to develop a kind of post-run lingering odor that even I’m not liking. I also bought a MEC t-shirt for running that is on sale and will get more if I deem it worthy.

I also–hold onto your hats–bought ankle socks, both for general use and for running. The latter even have a tiny bit of padding in the heel and the ball for extra support. I’ve never been excited about wearing socks before.

I was all set to try these multitude of new items today but the temperature rose so quickly in the morning that I had to cool my jets (ho ho) waiting for the temperature to peak and then start to decline in the afternoon, looking for that sweet spot to arrive where the heat would not be unbearable. I even spent some of this waiting time buying my first-ever hydration gear, a simple North Face belt and bottle. The belt is probably as close to minimal as you can get but still seems bulky to me. I toyed with just carrying the bottle in my hand. I wondered what I could do with duct tape.

I waited and watched as the temperature climbed to 35ºC (95ºF for those south of the border). This is not merely Africa hot, it’s too dang hot to even consider running. Much of the trail around Burnaby Lake is shaded but at 35 the air takes on an aspect that brings to mind a blast furnace.

And so it was that the rarest of things happened: I postponed a run because the weather was too nice.

It’s supposed to be a little cooler tomorrow. I shall try again then.

A pithy comment on the look of Office 2013

From Ars Technica reader jandrese:

For what it is worth, 2013 is also the ugliest version of Office ever. It looks like a web page where the style sheet failed to load.

This is an amusing and clever way of describing the whiteout approach Microsoft has used in the user interface for Office 2013. Rumour has it that we may see changes in the next version (for PC this will probably not be out for another year or more, though). I’m going to offer some of my own thoughts on UI design in iOS 7, Mac OS X, Windows 8 and a few miscellaneous others soon. In the meantime, have a look at the Ars Technica feature The software design trends that we love to hate. And you thought faux leather stitching was bad.