4 ms·
Oh please YES, the "not worth it", followed by an option to "please take me back to previous path before (because) latest fork = mistake". The very idea of judg
by K0SM0S 7y ago
Oh please YES, the "not worth it", followed by an option to "please take me back to previous path before (because) latest fork = mistake". The very idea of judging the overall travel is a good start (at the end, when they prompt you) but individual datapoints should be reportable as well. I'm pretty sure this would massively help build a dataset with "annotated" cases (good / bad) for RNNs.
> 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.
- johnmaguire2013 7y ago> please take me back to previous path before (because) latest fork = mistake 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.
- sjwright 7y agoThis is especially true in the UK where most rural roads are nominally 60 MPH even if they’re barely wide enough for two cars.