1703
When a real user uses the app
(lemmy.ml)
Post funny things about programming here! (Or just rant about your favourite programming language.)
I’m a user experience designer. My favourite story is from aviation engineering. I don’t remember the year or all the details, but the US Navy had put stupid amounts of money and time into engineering a new fighter jet. It was worked out on paper and built to exact specifications. Then, during the first human test of it, the pilot ejected on the tarmac before it took off. The plane crashed, obviously, but the pilot couldn’t explain what happened (apparently he had a concussion from his unscheduled landing).
The plane was built again, and shortly after takeoff, the pilot again ejected without explanation.
What the fuck was going on?
In the retelling I heard, someone finally noticed the design of the cockpit was to blame. In trying to cram all the standard controls plus new ones into the smallest amount of space, the designers had moved the eject lever right next to the lever to adjust the seat position – they’d coloured the eject lever red, but the pilot couldn’t see that since it was below and slightly to the right of his ass, and both levers were the same size and shape. Nobody noticed this was a problem until at least two pilots accidentally ejected on takeoff.
This might be apocryphal, I don’t know, but I learnt it as an example of how things might look good on paper, but you can’t really know until a user fucks everything up.
Id hardly call that a user fucking things up, that's not even good on paper. Those are a retarded pair of things to have next to one another regardless of any coloring on them. Especially with the same handles
I'm not a fighter pilot, but when I think "ejection", can't imagine anything but a high-stress situation where the pilot doesn't have time to figure out which is the ejection lever. Imagine a real emergency where the pilot grabs the wrong lever, gently slides back with the seat, and then fucking dies on impact.
"Gently slides back" 😂
My favourite story about aircraft design about some of the design mistakes on the F-16 fighter.
The F-16 was the first fly-by-wire fighter. They didn't have much experience with it, and tried out some new things. One was that instead of having a stick between the legs of the pilot they used a side stick. And, since everything was fly-by-wire they didn't need the stick to mechanically move. They decided they'd just use a solid stick with pressure transducers, since it was simpler and more reliable than a stick that moved.
The trouble was that the pilots couldn't estimate how much pressure they were using. This led to the pilots over-rotating on take-off (pulling back too hard). Even funnier was that at early airshows, when the pilots were doing a high-speed roll, you could see the control surfaces twitching with the heartbeat of the pilots as they shoved the stick as hard as they could to get maximum roll.
That led to them adding a small amount of give to the stick, essentially giving the pilots feedback on how hard they were pushing the control surfaces.
Another more subtle issue with the design was that originally the stick was set up for forward, back, left and right aligned with the axes of the plane itself. But, they discovered that when pilots pulled back on the stick, they were pulling slightly towards themselves, causing the plane to also roll. So, they realigned it so that "pulling back" is slightly pulling towards the pilot's body, rather than directly along the forward / backward axis of the plane.