- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
- ByteOnBikes ( @ByteOnBikes@slrpnk.net ) 142•1 month 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.
- RecluseRamble ( @RecluseRamble@lemmy.dbzer0.com ) 57•1 month ago
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.
- NeatNit ( @NeatNit@discuss.tchncs.de ) 38•1 month ago
I think they meant shoot in like a friendly way. You know, happiness bullets!
- KomfortablesKissen ( @KomfortablesKissen@discuss.tchncs.de ) 38•1 month ago
Oh, THAT’s what “friendly fire” means!
- tetris11 ( @tetris11@lemmy.ml ) 16•1 month ago
hey that tickles!
- abbadon420 ( @abbadon420@lemm.ee ) 9•1 month ago
Like how I always say to my friends, “Look at me again and I will fucking murder you and rape your family dog”… it’s just in good fun.
- CatLikeLemming ( @CatLikeLemming@lemmy.blahaj.zone ) English7•1 month 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.
- abbadon420 ( @abbadon420@lemm.ee ) 32•1 month ago
This makes want to become a tester. It scratches my evil itch just the way I like it.
- ClassifiedPancake ( @ClassifiedPancake@discuss.tchncs.de ) 26•1 month ago
I might be the one hitting that link just to see what happens.
- TedvdB ( @tedvdb@feddit.nl ) 23•1 month ago
Now the dev doesn’t need to comment this part of the code, saves him time.
- bratorange ( @bratorange@feddit.org ) 21•1 month ago
Day 492 of predicting edge cases…
- CanadaPlus ( @CanadaPlus@lemmy.sdf.org ) 18•1 month ago
Man, actually seeing this in a wild log would make my day.
- driving_crooner ( @driving_crooner@lemmy.eco.br ) 6•1 month ago
Is that python? If it’s, thank you, finally learned how to format text in a way that can be read on the script and in the execution.
- zaphod ( @zaphod@sopuli.xyz ) 8•1 month ago
As the other comments have already said it’s not Python. Not sure what you mean with text formatting, do you mean that it’s multiple strings that are concatenated using
+
? You don’t need the+
in Python, you can dosome_function( "part one of really long string" " part two of really long string" )
Which is identical to
some_function("part one of really long string part two of really long string")
- alfenstein ( @alfenstein@beehaw.org ) dansk3•1 month ago
Looks like TypeScript to me
- katy ✨ ( @cupcakezealot@lemmy.blahaj.zone ) 6•1 month ago
whats wild is that all the returned values were the same this is only for a log value that probably zero people check
- wizardbeard ( @wizardbeard@lemmy.dbzer0.com ) English10•1 month ago
I believe rule of thumb is to track/log at least one level deeper than what you show to the end user, to ease with troubleshooting and debugging.
Beyond that, logs are only useless until they aren’t, and then if you don’t have them you’re in for a universe of pain.