Re: Lost a fellow rider today

On Sep 24, 12:18 pm, "tomor...@xxxxxxxxx" <tomor...@xxxxxxxxx> wrote:
On Sep 24, 11:40 am, "David T. Ashley" <d...@xxxxxxxx> wrote:

Other things

Tim has already covered it well. I thought I'd add the following -
especially on the topic of when you approach people intending to turn
left or right:

In addition to the lane positioning and other things Tim mentioned,
make a practice of trying, if you can, to see things from the point of
view of the driver intending on making the left or right-hand turn.
As drivers/riders ourselves all know when people are most likely to
make rash moves; it's when the traffic preventing them from proceeding
is not giving them many opportunities. Then, when they glimpse an
opening they are more likely to shoot for it with less time spent
checking. They're concerned that, if they don't take that hole, it
might be a long time before another appears. A line-up of cars
waiting behind them (who get angry if the guy ahead misses an opening)
will only put on more pressure.

This is when you have to be especially careful. Like Tim says, watch
for that front wheel to move. Since movement there is easy to spot
and it will move even as the driver is in the process of transferring
his foot from the brake to the gas, it will give you the earliest
possible warning - and every split second really does make a huge
difference in these situations. Don't put much credence in the fact
the driver appears to be looking right at you. That don't mean much,
IMO.

Another aspect of seeing things from the driver's point of view is the
question of "when." You already know he wants to turn right/left.
The only question remaining is 'when', right?

So put yourself in the driver's place. If you were him and you are
trying to turn and there's a gap in the traffic permitting you to do
so, will you just sit there? Not likely. Okay, so how about, as you
are approaching the turner, you adjust your time of arrival to be just
a tad later, so that you make him wait a tiny bit? That way, by the
time you pass by him you will know with near certainty he has seen
you.

You know because, had he not seen you, he would have blasted through
already. The fact that he is still there can only be explained by the
fact he has seen you (since there's no other reason to wait) and, if
he hadn't seen you, at least you wouldn't have been broad-side to him
at the time he was most likely to charge through.

It's kind of hard to explain, but I hope you get what I mean. It's
like asking yourself the question, "If I were totally invisible to him
right now (which we sometimes are), what is the most likely instant in
time he will make his move?" Then just make sure you are not there at
that particular instant in time. The instant is not really that hard
to guess, actually. It is simply that point in time when, were it not
for you, a perfect gap has presented itself for him to charge
through.

So it's a bit of a timing thing - trying to not be in certain, bad
locations at the very worst times. That might also mean that you pick
up your pace a little to cross the danger zone slightly sooner - at a
time before the turner is still on his way to the intersection (on
highways you can see a long distance up the side roads) or while a
solid block of cars ahead (which you can join up to, beside them) is
making it impossible for him to turn. This is often better than just
getting there when you get there. Make a practice of this and what
you are doing is substantially reducing your risk long-term because
you will be less often in the danger zones at the times they are the
most dangerous.

Watch the front wheel. Adjust your speed up and down to arrive at
danger zones at the more optimal times. Try to see things from the
driver's perspective, especially with a view to predicting *when* he
will do the thing you already know he's intending.


.

Relevant Pages

  • Re: Effect of a rs485 damaged driver
    ... Tim Shoppa wrote: ... >>driver can affect the line by putting permanently the line in a high or low ... > Receivers can latch up/blow up too, for example by shorting one or both ... > resistors in series between each node and the bus wires. ...
    (sci.electronics.design)
  • Re: DBI BOF @ OSCON ?
    ... >>Is a patch available for Rudy to integrate? ... > found using the server is of course faster than emulation in the driver. ... Tim. ...
    (perl.dbi.users)
  • Re: WebCam Driver
    ... I just want to learn Device Driver Development. ... Tim if you somehow find the specs somewhere, ... I have a camera having VendorID: 0AC8 Prouduct ID: 307B. ...
    (microsoft.public.development.device.drivers)
  • Re: Disconnect webcam, how to recognize reconnection?
    ... Thanks, Tim. ... DirectShow was actually designed before hot-plug busses ... before ksproxy provided automatic filter wrappers around kernel ... driver could recover from a disconnect, ...
    (microsoft.public.win32.programmer.directx.video)
  • Re: Wakefield 2007
    ... In article <2f24aae64e.Tim@xxxxxxxxxxxxxxxxxxxx>, Tim ... Qercus 283. ... I'm just hoping we get enough feedback because Kathy & I who were intending to ... reporting on computers & computing since 1982 ...
    (comp.sys.acorn.misc)