2 ms·
Think back on how many times you've started a lane change and aborted because there was a car there, how many times you've looked down to navigate and hit the r
by rkagerer 3y ago
Think back on how many times you've started a lane change and aborted because there was a car there, how many times you've looked down to navigate and hit the rumble strip, how many times you've had to rely on ABS to avoid hitting the car you didn't notice stopping in front of you, etc.
I don't want to criticize your driving but these are not common occurences for me (ie. the answer to most is 'never'), and I would be quite concerned if they were. Most are solved by maintaining awareness around you (including checking blind spots) and follow distance ahead of you.
- y1n0 3y agoThis is BS. It takes a couple seconds to check a blindspot. Same with most other things you look at, navigation, radio, whatever. The rest of traffic doesn’t wait around while you are focused on that one thing.
- lutorm 3y agoI think his point was that the time to check the lane over is before you initiate a lane change, not after. About the only reason to initiate a lane change without pre-checking where you're going is if there's an emergency (like the incident we're discussing) and then it's questionable whether it's better to do the lane change anyway...
- ajross 3y agoLet's just say I've been astoundingly impressed at the quality of drivers on this forum. Come on, everyone stomps on their brakes for unexpected stuff, or has to jump back into the lane when it wasn't as clear as you thought[1]. You just code it, like almost all drivers do, as "someone else's fault", so it doesn't get filed away in your brain as something automation can fix. But it is, and I'm telling you straight up that it does. [1] Seriously, you see this happen around you hourly (or frankly more often) in urban traffic. You really think none of those drivers count?