Yeah, I've learned the smarter they try to make my device, car, etc. the more annoying it becomes in practice because of all the edge cases I seem to bump up against regularly.
For example, we have the greatest opportunity in a generation for someone to build "photoshop for text" i.e. a proper GenAI based LLM tool with similar design choices. LMstudio is the only even close example of this, and they're not getting it in the way that blender does.
For me its car's lane assistant, interfering with driving is big no for me. Asked my father to turn it off on their new mazda 3 too, 99% ok behavior is simply too low, even 99.9% would be.
Otherwise, in city driving, it's like some paranoid front seat passenger grabs the wheel every 30 seconds.
Of course, I always turn these stupid features off but, inexplicably, my wife likes them and keeps turning them back on. So when I happen to drive that car it continues to be a nasty surprise until I remember to turn it off. This also makes a separate UX failure even worse. Settings like seat position, enter/exit behavior, navigation and even entertainment options are stored and recalled in per-driver settings. These per driver settings can also be linked to each key fob. She has her fob and I have mine. Very nice - except these damn driver "assist" features are NOT stored in per-driver settings like they obviously should be!
Damn it, car UX designers - all user options should be stored per driver. It's a few KB for bit flags and single-byte values, it's not like we don't have the storage these days.