Thanks to the well-wishes from everyone. I'm fine and safely home. If the recovery keeps up, I'll probably have another post in time for Tuesday just thanks to sheer boredom =D
Amusingly, I've observed the opposite problem too. I work on a product that has a bootable environment with a command-line interface for, among other things, installation. A small number of users go on auto-pilot and hit the sequence of buttons that we intentionally tried to make hard to do: they proceed from the first menu with the first option for installation, then type out something to the effect of "DELETE EVERYTHING SAVED" spelled correctly and all in capital letters. Yet, here I am still typing "y" to scripts that want me to type "yes" and wondering why they they don't proceed. Maybe we should take the instruction of what to type out of the CLI and put it in the installation guide instead.
oh oh, this autopilot thing happens to! recently worked on a backup feature that would clobber your installation if you do an in-place install, so it fails safe by making you specify where you're restoring to. And like a ton of restores "fail" because most people just go w/ the failsafe mode and are forced to try again. I think a lot of modern discussion about this are about 'self-driving' cars where humans are known to just zone out and 'trust' the inherently untrustworthy system.
I think having things like enforced checklists in aviation, or deliberate fail safely mode is one of the few guardrails against this. There's probably other ways that I just haven't encountered
Thanks to the well-wishes from everyone. I'm fine and safely home. If the recovery keeps up, I'll probably have another post in time for Tuesday just thanks to sheer boredom =D
"Toot a horn" lmao
Amusingly, I've observed the opposite problem too. I work on a product that has a bootable environment with a command-line interface for, among other things, installation. A small number of users go on auto-pilot and hit the sequence of buttons that we intentionally tried to make hard to do: they proceed from the first menu with the first option for installation, then type out something to the effect of "DELETE EVERYTHING SAVED" spelled correctly and all in capital letters. Yet, here I am still typing "y" to scripts that want me to type "yes" and wondering why they they don't proceed. Maybe we should take the instruction of what to type out of the CLI and put it in the installation guide instead.
oh oh, this autopilot thing happens to! recently worked on a backup feature that would clobber your installation if you do an in-place install, so it fails safe by making you specify where you're restoring to. And like a ton of restores "fail" because most people just go w/ the failsafe mode and are forced to try again. I think a lot of modern discussion about this are about 'self-driving' cars where humans are known to just zone out and 'trust' the inherently untrustworthy system.
I think having things like enforced checklists in aviation, or deliberate fail safely mode is one of the few guardrails against this. There's probably other ways that I just haven't encountered