Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think there's some room for improvement though. Instead of "just one human in there", they could put them out in teams of two, and have periodic "awareness checks" that you have to respond to by pressing a driving-irrelevant button.


Dead-man switches do not work.


Don't work for what purpose, according to whom? Are you sure that applies here?

What I suggested there isn't really a deadman's switch ("stop if no one is around to do task x"), but something to periodically, randomly check the driver's attentiveness, and can raise a red flag if they take too long to respond.

A deadman's switch is different and enforces "do X if person Y stops doing this thing at this predictable interval" -- not what I was proposing.


Vigilance control. But even these fail with more experienced users, similar to how alarm clocks fail some people (they wake up just enough to get up and turn the alarm off, then continue sleeping).


Vigilance control. But even these fail with more experienced users, similar to how alarm clocks fail some people (they wake up just enough to get up and turn the alarm off, then continue sleeping).


I was proposing it as a way to validate engagement by the testing teams, not the mass market.


Like I said, these are especially hard to get right for frequent users, presumably your testing teams would log a lot of hours on these - just like train drivers, which have had this exact same problem.


Yes, you said it several times, just not with a citation or other means of grounding your claims that might lead us to a way of resolving the disagreement productively.


they do but they must be very random so you can't activate them when asleep.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: