3 ms·

If i was a surgeon and "held it wrong" I'd probably get sued or fired. If i was a welder and "held it wrong" I'd get a written warning, which later might end u

If i was a surgeon and "held it wrong" I'd probably get sued or fired. If i was a welder and "held it wrong" I'd get a written warning, which later might end up in a termination. If i use ssh-keygen wrong in production because i did not read the documentation... then its the tools fault for not having sane defaults?

bombcar 4y ago
If you were a pilot and "held it wrong" you'd probably be dead, and Boeing would get away scott-free ... the first time. Somewhere between "everything is a death-trap, learn how to use it" and "this device is perfectly safe, because it cannot do anything" lies the mean we need to hit.
- blueflow 4y ago
  Not reading the available documentation for your tools is neglience either way.
  - jacquesm 4y ago
    I'm willing to bet a pretty good sum of money that no professional programmer has read all of the available documentation for all of their tools.
    - blueflow 4y ago
      Yeah, that does not happen either, but it would be nice if professional programmers would at least try to read it instead of relying on reddit, stackoverflow and random peoples blogposts.
  - afiori 4y ago
    That is why it is allowed to buy morphine by the pound at Wallmart, you are trusted to understand the consequences and use it right. More seriously, the actual objective is not blaming the guilty but rather avoiding the problems. If system A interacting with system B is likely to causes an incident then either A, B, or the interaction need to change. For surgeons all three have happened, the same for airline pilots. The surgeon had to swear very convincingly to have "read the documentation" before being even allowed to think about "holding it wrong". In the case of people using GPG wrong the only solutions you have is to make is easier to "hold right" or make is so heavy and painful that anyone without true determination gives up trying to "hold it" at all.

bombcar 4y ago

If you were a pilot and "held it wrong" you'd probably be dead, and Boeing would get away scott-free ... the first time. Somewhere between "everything is a death-trap, learn how to use it" and "this device is perfectly safe, because it cannot do anything" lies the mean we need to hit.

blueflow 4y ago
Not reading the available documentation for your tools is neglience either way.
- jacquesm 4y ago
  I'm willing to bet a pretty good sum of money that no professional programmer has read all of the available documentation for all of their tools.
  - blueflow 4y ago
    Yeah, that does not happen either, but it would be nice if professional programmers would at least try to read it instead of relying on reddit, stackoverflow and random peoples blogposts.
- afiori 4y ago
  That is why it is allowed to buy morphine by the pound at Wallmart, you are trusted to understand the consequences and use it right. More seriously, the actual objective is not blaming the guilty but rather avoiding the problems. If system A interacting with system B is likely to causes an incident then either A, B, or the interaction need to change. For surgeons all three have happened, the same for airline pilots. The surgeon had to swear very convincingly to have "read the documentation" before being even allowed to think about "holding it wrong". In the case of people using GPG wrong the only solutions you have is to make is easier to "hold right" or make is so heavy and painful that anyone without true determination gives up trying to "hold it" at all.