this post was submitted on 12 Aug 2024
1008 points (99.5% liked)

Programmer Humor

19512 readers
339 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 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] ByteOnBikes 223 points 2 months ago* (last edited 2 months ago) (25 children)

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.

[–] RecluseRamble@lemmy.dbzer0.com 82 points 2 months ago* (last edited 2 months ago) (5 children)

And we absolutely wanted to shoot the tester who gave us this use case.

Why? Because he tested well and broke the software? A user changing their mind during a guided activity absolutely is a valid use case.

[–] CatLikeLemming@lemmy.blahaj.zone 8 points 2 months ago

It's likely a difference of emotion compared to logic. Emotionally they'd think "Damn it, now we need to check for such a weird specific edge-case, this is so annoying" while logically knowing it's better the tester caught it.

load more comments (4 replies)
load more comments (23 replies)