I would not be quick to make assumptions like this. He could have experienced the issue like 1/20 times, and intended to remind himself to watch out when he gets to that spot. And maybe he forgot this time. It’s easy to get into a trance on long repetitive drives. It isn’t like he immediately did back to back drives and changed nothing the second time.

And that’s the problem with an “autopilot 99.9% of the time, but still pay attention just in case” feature.

Which is why Waymo never released half self driving technology, their early tests showed that even if they told Google engineers that they were being recorded and they'd be fired if they didn't watch the road, in a few weeks a lot of them trusted the software too much

Source?

It is not suicidal, but probably worthy of a honorable mention in the annual Darwin Awards roundup since it was a very bad judgement on his part.

As an engineer - he should have known better than to continue to use the feature the moment it became unreliable for reasons unknown. Those kind of failure modes are extremely devious killers.

So all the engineers who experience a BSOD, they discontinue using Windows immediately after?

This is exactly what the navy did when the bsod parked that destroyer in a harbour 20 years ago.

When you have mission critical pieces of software (aka stuff that kills you) starting to behave in unexpected ways with unknown failure modes you stop using it asap until fixed.

I will gladly continue using my bsoding pc for gaming, but I won't use it in data center or to control a shuttle launch.

If a person uses gas oven that leaks from time to time and only a bit - how will you classify him.

Totally not the same thing. If my car's steering locks up and I can't turn because of a software glitch, I'm returning that thing to the dealer ASAP.