41–50 of 369 posts
Earlier quoted context omitted.
I’m sorry for bringing this up here, but why do I need to scroll sideways in Safari on iphone on Hacker News every time there is a quote written in an unproportional font? Just, why?
Because he used block quote syntax. It's designed for code on HN's implementation, so it preserves newlines, instead making you scroll. It's a poor choice for quoting non computer languages.
The real cause of the collision was poor seamanship and failure to follow the COLREGS on the part of the bridge crew of the destroyer. Most specifically they were seriously in violation of Rule 6: the Safe Speed Rule http://navruleshandbook.com/Rule6.html Every vessel shall at all times proceed at a safe speed so that she can take proper and effective action to avoid collision and be stopped within a distance appropr…
The path to a disaster has been compared to a tunnel [0]. You can escape from the tunnel at many points, but you may not realize it. Trying to find the 'real cause' is a fool's errand, because there are many places and ways to avoid the outcome. I do take your meaning, reducing speed and following well established rules would have almost certainly have saved them. 0. PDF: http://www.leonardo-in-flight.nl/PDF/FieldGui…
In a lot of fields where the stakes are high and mistakes are costly (aviation and emergency services are the two I'm most familiar with) the analogy used is a chain. Break any link in the chain and you prevent the event.
https://www.aopa.org/asf/publications/inst_reports2.cfm?arti...
The real cause of the collision was poor seamanship and failure to follow the COLREGS on the part of the bridge crew of the destroyer. Most specifically they were seriously in violation of Rule 6: the Safe Speed Rule http://navruleshandbook.com/Rule6.html Every vessel shall at all times proceed at a safe speed so that she can take proper and effective action to avoid collision and be stopped within a distance appropr…
The path to a disaster has been compared to a tunnel [0]. You can escape from the tunnel at many points, but you may not realize it. Trying to find the 'real cause' is a fool's errand, because there are many places and ways to avoid the outcome. I do take your meaning, reducing speed and following well established rules would have almost certainly have saved them. 0. PDF: http://www.leonardo-in-flight.nl/PDF/FieldGui…
UI flaws have hit the Navy before, with even worse consequences [1]. [1] https://en.wikipedia.org/wiki/USS_Vincennes_(CG-49)#Iran_Air...
Nothing I see in that article (or anything else I've seen about the incident) attributes it to a UI issue. Not all errors made by users are the fault of the UI.
I learned about the incident in my computer ethics class in college (along with Therac-25, etc).
Quickly-skimming, it looks like Cracked has a decent writeup of the UI issue specifically [1].
[1] http://www.cracked.com/article_19776_6-disasters-caused-by-p...
Earlier quoted context omitted.
That is super dumb and dangerous. They should just flip the inputs on one end. EDIT (since some people obviously don’t understand the problem): ... so that each set of controls is always correct for the respective side on which it is located. No switch is necessary.
No, they just have a big button by each wheel marked "MAKE THIS THE BOW".
Amazing that someone would design in multiple steering wheels, only one of which is active, and no big indicator to make it super-obvious which one it is. Also amazing that there's a mode where moving a control sometimes controls all engines, sometimes just one.
Airbus uses two "side stick" controllers that are on opposite sides of the cockpit. This was a contributing factor in the Air France 447 crash.
Earlier quoted context omitted.
The path to a disaster has been compared to a tunnel [0]. You can escape from the tunnel at many points, but you may not realize it. Trying to find the 'real cause' is a fool's errand, because there are many places and ways to avoid the outcome. I do take your meaning, reducing speed and following well established rules would have almost certainly have saved them. 0. PDF: http://www.leonardo-in-flight.nl/PDF/FieldGui…
I've never heard the tunnel analogy. Seems odd, since tunnels generally only have one entrance and one exit... In a lot of fields where the stakes are high and mistakes are costly (aviation and emergency services are the two I'm most familiar with) the analogy used is a chain. Break any link in the chain and you prevent the event. https://www.aopa.org/asf/publications/inst_reports2.cfm?arti...
Earlier quoted context omitted.
Hearing (one of many) alarms is one thing. Feeling the control wheel or stick fighting you is far more direct. AF 447 was absolutely a UX failure.
If you're going to go against the conclusions of the accident report, which is very thorough, you'll have to do more than just assert that the side sticks were responsible. Check it out here: https://www.bea.aero/docspa/2009/f-cp090601.en/pdf/f-cp09060...
Earlier quoted context omitted.
Because he used block quote syntax. It's designed for code on HN's implementation, so it preserves newlines, instead making you scroll. It's a poor choice for quoting non computer languages.
More importantly, in mobile the code block's width is only 200 pixels.