Disagree. The purpose of the indicator is to signal your intention to others. Indicate first, then shoulder check. If you then discover a car in your blind spot, abort the manoeuvre if necessary or slow down to let them pass you first.
I do agree it's bad form to indicate when you know there is a car in your blind spot already.
Discovering a car in your blind spot should be a relatively rare occurrence if you are driving attentively.
This is great news for me. Recently I have been trying to set up a simple
solution to replicate a MySQL database into DuckDB, without the whole CDC shebang (kafka, debezium etc.). The biggest problem I faced was the fact that
cascaded operations are not captured in the logs and so they would not make it into the replica. Every workaround I could come up with was slow and/or fragile. It sounds like these up-coming changes will simply make that problem disappear - hurrah!
This. And I do their work a lot more slowly because it's not my regular job, and I actually already had to do some of the work (getting the items out of my trolley and onto the conveyor). Now I stand there forever fumbling with barcodes, trying to get bags to stay open, switching between getting items out of the trolley and scanning. The old checkout system is so much more efficient when you are buying anything more than a couple of items at a time.
I do agree it's bad form to indicate when you know there is a car in your blind spot already.
Discovering a car in your blind spot should be a relatively rare occurrence if you are driving attentively.