This lack of understanding and emphathy goes a long way.
- Perhaps the cycle way had issues that made it un-navigable. Maybe it got tacked, had a load of glass, perhaps it was not smooth. You don't really know how bad some off-road areas are until you are 2 feet away (then you notice, oh yeah, this is rooted to crap, or there are other issues).
- Maybe the cyclist needed to make a turn that was coming up?
- Maybe the cyclist had joined the road way not long ago and was going to hop over
- Maybe the road way was just safe enough rather than go on a path that significantly reduces speed of travel. A 20% reduction in speed, every day, two ways, over distance - adds up. It's not quite enough for something to be "safe", needs to be functional as well. If you make a commute be an hour when it could be 20 minutes instead, that infrastructure is not "perfect" (that is a real example, some infrastructure I've seen wants you to ride on super crowded side-walks where you can do at best 3mph for 2 miles. On the road that goes by in about 5 minutes, can sustain 25mph on it and 2 miles is done in no time; and this is just one two mile stretch of a 6 mile distance).
> he's proof that even the best infrastructure
It turns out what looks like "the best infrastructure", is really often a sad joke when you try to ride in it. Protected lanes sound nice, but turning left (in the US) out of one is a nightmare and is super dangerous because nobody can see you or is expecting for you to cross lanes.
This again goes back to perspective. Those protected lanes might seem lovely, but in practice can be totally useless. The far edge of the road might look ideal, but if you look at it you'll see it's uneven, full of debris, has grates, and places where the road crumbles away and is not even there. You won't notice these at all traveling faster than 20mph (let alone at 50mph) and from 20 feet away.