this post was submitted on 10 Apr 2024
1697 points (99.0% liked)
Programmer Humor
32559 readers
622 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One of the things I like most about my customer-facing technical role is that users find the craziest bugs. My favorite is a bug in a chat program that would keep channels from rendering and crash the client. The only clue I got was "it seems to be affecting channels used by HR more than other departments, but it's spreading."
Turns out the rendering engine couldn't handle a post that was an emoji followed by a newline and then another emoji. So when the HR team posted this, meaning "hair on fire" it broke things:
Gotta love user reported bugs. I had one that reported a product of ours crashed only on Mondays. We spent a total of 5 minutes thinking of a cause and appointed customer support for a Friday morning. Lo and behold the app still crashed.
In this case the app only crashed on Mondays... because that's when this user actually used the application
Before we had mindblown emoji, we had this.
Before that we had โฝ:-)
User reported bugs can be wild. I had one where the user was tapping a button repeatedly so fast that the UI was not keeping up with the code and would no longer sync certain values properly. I'm talking like tap the button 15 times in a second. Another issue involved flipping back and forth between the same page like 10 times then turn the device Bluetooth off and immediately back on.
Why the fuck are your users flipping a page back and forth 10 times. I understand the Bluetooth bit, they wanted it to restart probably from a device not showing up. Also what was the issue
I can't remember what the exact issue was that was produced by those steps. I want to say it was some sort of visual bug where parts of the page wouldn't load. I do know that it only happened if you toggled Bluetooth within seconds of flipping the pages so many times. I honestly have no idea why the user decided to change pages so many times. You could take a little bit of time changing the pages, so maybe they kept viewing a page and backed out only to want to view the page again?
Why would you post this, my phone exploded and took a shit. I didnt know it could do that.
Be thankful it didn't take an explosive shit.
Don't worry, I had a bit too much to drink last night so it's covered
I did actually find a very similliar bug in the experimental rendering engine of element (the matrix client). So yes, this is something that exists somewhere else too.