Stupidest product design you’ve experienced

I’m shocked to hear that a corporation is just in it for the money.

My only beef is how after you’ve selected the fuel, the pump starts beeping too many times.
Lost weeks and weeks’ worth of sleep over this.

The loud pump commercials that drive you inside to get away from them. I’ll never buy anything from these places. “Why is the gas pump yelling at me???”

How about a touch screen on a toaster?

Totally agree! Sometimes you can temporarily mute them by pushing various buttons, but that only seems to work at some stations.

The noise actually forces me to the other side of my vehicle where I can’t monitor the gas pump.

At one station here in my town, I can’t get away from the noise because there is a cacophony of all of the gas pumps screaming advertisements at top volume, even when not in use.

I’m surprised to learn that some stations are still using those. I haven’t seen them in a few years, and the specific stations I’ve used that had them have taken them out. I was under the impression that the industry had learned that they were counter-productive. I guess not.

Who are these people? A touch screen on a toaster, that asks you questions?

What is the square root of 5,832?

Was that meant for some other thread?

****** <>

Incorrect… Toasting Disabled!

Incorrect answer: Toaster turned ON …

to turn OFF, input the correct answer…

… and dont lose your concentration because of the 125dB fire-alarm

I had to do some online paperwork for my job.

This required setting up a password, as well as yet ANOTHER authenticator app on my phone.

I logged back in later, and it insisted on sending a code to my email.

I did that, and it still wanted a password and the code from the app. Multiple times.

On another website years back, I had to set up a password. At least X number of characters, upper/lower - the usual. So I set something up like P@ssword123ABC123ABC.

It took it.

I tried logging in again. It refused.

I did yet another reset - similar password length etc. Lather, rinse, repeat.

I don’t know WHAT made me try a SHORTER password - say, P@ssword123. That one, it took AND let me log in again.

Seems there was an undisclosed maximum length. It would compare the long password, but it only saved the cache for the shorter one - so of course what I input never worked.

And on yet another system: minimum length of, say, 14 characters. I had a pattern I used that was 16 characters. It never worked. I called the help desk. They said “so try EXACTLY 15 characters” and that worked.

In both of those cases, the *&%^ INSTRUCTIONS WERE WRONG.

Salesforce has infected Slack with enshitification. This is stupid design on purpose to push paying customers into higher cost tiers.

We pay for the business or pro or whatever level of Slack. It used to just be the “paid” version, instead of free, but now many levels to buy. Slack charges per active user. Slack also has the concept of guest users on a paid instance. The guest users can only participate in one channel, but do not cost anything.

Guest users now expire after 30 days.

Changing the default guest expiration time requires the highest paying tier, “enterprise”. Bulk setting the expiration date of existing guest users requires enterprise tier. Sorting the list of existing users by type requires enterprise tier. Adjusting expiration dates programatically with the API requires enterprise tier.

As a paying account, I need to scroll through the list of all my users looking for guests. When I find a guest it requires 6 clicks to move their expiration date out a year.

Still better than Teams.

We fit 11 one time. Although one guy’s legs were completely outside the window. When you’re a teenager, you’re immortal.

This may be a design issue or just user error, but I have a Norelco hair trimmer that I use for buzzing my hair every week or so. The power button is about halfway up on the back side (away from the trimmer blades) - exactly where my thumb rests as I’m holding the trimmer. And as I’m running the trimmer across my head, I will often accidentally turn it off with my thumb (ow!). If it was higher or lower or on the other side, or a slider switch instead of a push button, it wouldn’t be a problem.

I’ve got a two Hunter Fans and three remotes for them (I have two remotes for one of the fans) and all of them have a design issue so stupid and so easy to fix, I honestly can’t believe they made it to market in their current form. And based on not being able to find a good picture on the internet, I’m guessing they’ve since changed it.

In any case, this isn’t the same version I have, but close enough:

The problem is that, the remote ‘hooks’ on to the holder at a point below the buttons. That means any time you push the button, you have to brace the bottom of the remote or it just falls off. All they had to do was move the buttons down or the hook (and the part on the remote that catches it) up higher. The buttons have to be below, or at least closer to, the center of rotation. Even a bump out on the back of the remote would fix it.

I do see the holders they come with are now more like ‘pockets’ that they drop into, which should fix that problem.

Also, one of the remotes has an LED so bright, even in daylight, I make sure I’m not looking at it when I hit the button.

I had a job once at a community college, where I had to set up an email account. It kept on giving me the error message “length or complexity requirements not met”, and so I kept on making the password longer and more complex.

Eventually, I just hit the button for it to suggest a password. It was a six-letter word followed by a digit. My passwords didn’t meet the “length or complexity” requirements because they were too long and complex.

Good security design for UIs is all about not leaking info via errors or error messages. IOW don’t give the bad guys hints.

But input validation errors are the opposite; you have to tell the user what the happy path is.

Dumb shit happens when somebody thinks that because passwords are part of security, you want the uninformative messages. Frickin’ morons.

Nowadays when I see restrictive PW complexity requirements I immediately suspect they store them in plaintext. Yikes :grimacing:

I was just doing something on the TreasuryDirect.gov website and had to complete one of the security questions that involved the name of a friend from high school. I tried entering “Robert Smith” but that didn’t work. Fortunately I kept records of the responses I provided when I set up the account because I entered “Bob Smith” originally.