1023
you are viewing a single comment's thread
view the rest of the comments
[-] ByteOnBikes@slrpnk.net 228 points 1 year ago* (last edited 1 year ago)

At my job, we have an error code that is similar to this. On the frontend, it's just like error 123.

But in our internal error logs, it's because the user submitted their credit card, didnt fully confirm, press back, removed all the items out of their cart, removed their credit card, then found their way back to the submit button through the browser history and attempted to submit without a card or a cart. Nothing would submit and no error was shown, but it was UI error.

It's super convoluted. And we absolutely wanted to shoot the tester who gave us this use case.

[-] Jerkface@lemmy.world 143 points 1 year ago* (last edited 1 year ago)

Better the tester than a user.

[-] chevy9294@monero.town 48 points 1 year ago
[-] FreshLight@sh.itjust.works 65 points 1 year ago

As of now, I consider you an enemy

[-] filcuk@lemmy.zip 37 points 1 year ago

Are you from microsoft?

[-] slampisko@lemmy.world 25 points 1 year ago

Being prepared for the eventuality, knowing the consequences and deciding what to do about it before it happens for a user.

[-] RecluseRamble@lemmy.dbzer0.com 18 points 1 year ago

Different mindset. A user doesn't want to find bugs but get shit done.

[-] normalexit@lemmy.world 9 points 1 year ago

Brand reputation?

[-] danc4498@lemmy.world 1 points 1 year ago

Users are dumb, testers are assholes.

[-] jaybone@lemmy.world -2 points 1 year ago

Sometimes testers are also dumb. Most times.

load more comments (2 replies)
load more comments (17 replies)
this post was submitted on 12 Aug 2024
1023 points (99.5% liked)

Programmer Humor

27898 readers
2152 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS