> I’d often prefer a slightly slower route that’s less work to drive.
Me too, and I suspect most people — like, when is it ever a good option to avoid a free highway to save 1 minute when the driving is twice or more fatiguing? Are we bodyless machines or animals with a concept for "tired" and "attention"? This is where I feel recent evolutions in DL have been, perhaps, more for the benefit of developers and researchers (efficiency), and maybe not for real human benefits on the user side.
I don't claim the problem is easy, but I know second-hand that what users want and what AI projects solve for may be two very different X.
Seriously. I regularly travel from Ohio to Michigan and back, and often times if I take an exit for gas, Google Maps will assume I want to take an obscure country backroad for the final 2 hours rather than get back on the highway.
I absolutely do not want to worry about deer, a lack of gas stations, food, and light.
She’s certainly not wrong that from a UX perspective, simple can be really nice, especially if you’re driving on crowded roads and want to focus on driving.
It feels like cheating to the other drivers who didn’t take the “short cut” and leads to delays all around due to the extra merging going on. (exhibit A: I-85N vs. I-285 in Atlanta, aka Spaghetti Junction)
Maps really need a “not worth it” features for tiny optimizations. I’d often prefer a slightly slower route that’s less work to drive.