I just got invited to a meeting for a time zone that doesn’t exist this time of year. In the US EST does not stand for Eastern time, it stands for Eastern Standard Time (~November-~March), EST is not an active time zone, it is EDT Eastern Daylight Time. Its a pointless thing, most people probably don’t notice, but its wrong.
Fake internet points to anyone who knows why DB-9 bothers me.
Edit: corrected a missing n in an eastern
My wife’s car has a emergency brake PADEL (not pedal) on the dashboard that is connected on one end and you can push down on the other end or loop your finger under the padel and pull up (like a button version of a diving board). You push it to turn on the Emergency Brake, and once on, you pull it to turn it off. But what if it’s off and you pull it? Nothing. If it’s on and you push it? Nothing. This button takes 2 inputs but depending on its current state only 1 input will do anything. It’s bad UI/UX in the real world.
Here’s a stock photo of the kind of button but in a different car than my wife’s.
Of course you are welcome to be annoyed by whatever you want but I think I kind of agree with this design… Regardless of what state the car is in, you always know that if you push that button, the car should now be in park. If you’re a dum dum like most of us, and you forget whether you’ve done it already or not, you don’t need to check the dash or anything to decide whether to push it or not, you can just do it. It’s like saving twice in a Pokemon game. I like that it’s two distinct gestures, but compressed down into one mechanism.
However, I’m not sure I like that it’s push to engage and pull to disengage. In my car I’m pretty sure it’s pull to engage and push to disengage, which reminds me of the old lever style of parking brake.
Truth is, I made up which way was which because nothing about this push-pull paddle expresses which direction is which action and I can never remember. Every time I interact with it is a guess. Do it one way, if I was wrong then do it the other. I’m onboard with idempotency but I feel this trades clarity for it.
I think that’s actually good UX from a safety standpoint. It means the button is “idempotent”: doing an operation the first time puts it in a state, and then doing it again leaves it still in that state.
If you’re in a moment of panic and want the brake on, you might push the button a bunch of times in quick succession to “be sure.” If it were a regular button, this would rapidly toggle it on and off, which would leave it in an uncertain state after you pressed it so fast. This way it turns on and stays active until you are ready to turn it off, and then you do another idempotent operation to turn it off. I don’t think all buttons should be like this, but I think it’s a good design decision for a button used in an “emergency.”
