Before I do anything "risky" with forms I copy the text AND paste it somewhere else to confirm I really copied it. Only then do I take the next action, and still I get burned all the time by crap like this one way or another.
this post was submitted on 01 Sep 2023
144 points (97.4% liked)
Programmer Humor
19817 readers
555 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I usually just start from typing it up in emacs, then copy paste it to the fussy little form. Anything over six words, it probably saves me time, even if nothing was going to go wrong. And then... Just as you said.
I recently had a complaint form refuse my complaint because it was too rude!
There wasn’t any bad language in it at all. I removed the sentence "It's now more than two months since the accident and I would have expected the repairs to have been completed by now” and that let it through - sensitive or what?
I once had the opposite experience. Calmly and amiably complained about an employee misbehaving, but got asked aside by the manager to talk. She asked me to put the complaint in writing through their system and, looking directly at my eyes, added “Please feel free to be as explicit and emotionally expressive as you want. Don't refrain from expletives, rudeness and bad words. We would really, really want to understand the extent of your upset over this situation, you know what I mean?” That's when I realized that she wanted to fire this employee guilt free and was asking me to give her the ammo for the firing squad in front of HR.
I'd post the full complaint to a site like Pastebin, then share the link with them.
Though I wonder: if they limit the text to 250 characters, do they even care to read the complaints at all...
I know of a certain big company that has a bug report UI in one of their main products that literally goes nowhere, it used to go to a table in the db, then they removed the table since it was not really used and they wanted to get more storage, so someone quick fixed the bug report to go to a Google sheet
Nobody really checks that sheet and it is not automated or used for anything at all, the person that created that sheet was also deprovisioned some time ago.
Also since many things have changed the only thing that is pulled to the sheet is the first field to specify the category of the bug, all the descriptions, files, photos, logs and more granular items are just not going anywhere.
When this was reported the only reply from management was "QA will check it later" this was 2 years ago so...yeah
At 250 char no one is reading it. They're just doing sentiment analysis and scanning for common words
It's a legal complaint. Someone is going to get fined, likely thousands of dollars, if the complaint is substantiated. I strongly suspect a human will be reading the whole thing more than once, before proceeding to gather much more info.
It's like raiiiiiiin
On your wedding day
It's not a request, it's a challenge.
To be fair, if the interface let you add a lot of information, the instruction would be way too hard to comply with.
Well can you attach it when you fill the 250 characters?